LinuxCNC 2.10 build

I started a build for new CNC plasma table so here's my starting point.

CPU Ryzen 5 6C/12T 3.2Ghz 32G RAM, 550G SSD, Dual Ethernet ports
Ubuntu 24.04.02 - I know it's not "debian" but is what all other machines here run. Compatibility and support are the key deciding factors
PREEMPT-RT installed, Fairly minimal system with snap completely removed.
Stepper Drives (4ea) Stepper Online DM542T - have had excellent results with these in the past
Stepper Motors (4ea) Stepper Online 23HS30-2804S - again have worked well in past
Custom built frame from 2x2 16ga steel tubing. All Linear Rails SBR20. All Ball Screws SFU1605
Motion Controller Mesa Electronics 7i95T & THCAD2 - ordered and expected arrival in next few days
LinuxCNC version 2.10 being built from source.

I can successfully build the rip version without error and it appears to work correctly however as I mentioned I do not have the 7i95T in hand quite yet and it's not listed as an option in the opening config choices.

To get the full package I'm working to compile to get the .deb version and having some make problems.

Problem 1
I get lots of errors during the build of man pages. Some work but many report this error and often multiple times.

Making manpage sampler.9
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'

I suspect this has to do with the fact that Ubuntu 24.04 uses python3.12. I haven't dug into to it but have had many problems in many projects with python version compatibility and this is known issue from 3.11 to 3.12. Any suggestions on how to fix this are welcome and sooner or later it'll have to be addressed anyway.


Problem 2
This is the end summary of the build

Compiling module_helper/module_helper.c
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
Compiling localized message catalog ../share/locale/ar/LC_MESSAGES/linuxcnc.mo
Compiling localized message catalog ../share/locale/bg/LC_MESSAGES/linuxcnc.mo
cc1: all warnings being treated as errors
make[2]: *** [Makefile:278: objects/module_helper/module_helper.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/plasma/Documents/linuxcnc-source-dir/src'
dh_auto_build: error: cd src && make -j12 build-software returned exit code 2
make[1]: *** [debian/rules:55: override_dh_auto_build-arch] Error 2
make[1]: Leaving directory '/home/plasma/Documents/linuxcnc-source-dir'
make: *** [debian/rules:43: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

The _FORTIFY_SOURCE error shows up many times as well and probably isn't the only problem.

Again I know it's not debian but Ubuntu is derived from debian and the rip version compiles and works so I've very optimistic once I work out a few kinks this will too.

cc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.

Thanks for any and all suggestions. Mike

As Tommy said, balls screws are a poor choice as you can't get the speed out of them and they whip.
Either belts or rack and pinion (with 3:1 to 5:1 reduction)
nodocs has changed. refer the docs

linuxcnc.org/docs/devel/html/code/buildi...nc.html#_build_modes

Thank you for your responses.

I tried the following:
DEB_BUILD_OPTIONS=nodocs dpkg-buildpackage -uc -B
DEB_BUILD_OPTIONS=nodocs dpkg-buildpackage -uc -b
and a few others but always get exactly the same result.

looking at man dpkg-buildpackage I see
-b equivalent to --build=binary or --build=any.all
-B equivalent to --build=any

nodocs isn't an option for DEB_BUILD_OPTIONS by default but it does note "that other options honored by debian/rules might be defined by distribution specific policies." So now I'm off chasing that down.

I also noted that under man dpkg-buildflags(1) there is some interesting info on fortify. I'll chase that later if that problem remains.

Could (I suspect) be distro related so I expect some settings/options will need to dialed in.

yeah sorry about the typo in the title. should have been 2.10

So I found a quick fix for the _FORTIFY_SOURCE errors which is ok specifically for me at least to now but not a good fix for the project.

In the src directory is Makefile line 255:
original line DEBUG := $(DEBUG) -g -Wall -D_FORTIFY_SOURCE=2
modified line DEBUG := $(DEBUG) -g -Wall

in the Makefile.inc file line 114:
original line CPPFLAGS = -Wdate-time -D_FORTIFY_SOURCE=3
modified line CPPFLAGS = -Wdate-time

As I mentioned, this would not be an acceptable fix for generalized distribution as buffer overruns and other security features provided by _FORTIFY_SOURCE are important. It does however get me going for now just fine.

Now I'll dig into the manpage issue with "\S" and see if I can find a workaround for that. Documentation is always a good thing to have.

Thanks to all for help and suggestions.

Quick update and correction.

It seems that changing the Makefile.inc isn't necessary as it gets rebuilt as part of the run.

So looking at ./debian/configure I see the option for no documents is 'no-docs' and this works.

./debian/configure no-docs
dpkg-buildpackage -b -uc

-b option doesn't seem to matter.

I'll do some more digging into the fortify issue to see if I can find a better solution and to understand the DEBUG question lingering in my miind.

Cheers