Problems building ntpsec on Arch (AUR)

James Browning jamesb192 at jamesb192.com
Fri May 30 09:43:28 UTC 2025


On Thursday, May 29, 2025 4:14:16 PM Pacific Daylight Time Gregory Boyce via 
users wrote:
> Hello,
> 
> I've been maintaining the ntpsec package in the Arch User Repository, and
> I've been encountering a couple of issues with the new 1.2.4 package.
> 
> The first issue is the endianness check causing a failure, but only when
> building with makepkg.
> 
> Here are the commands I use in the build:
>   ./waf configure --prefix /usr --sbindir=/usr/bin --refclock=all
> --enable-leap-smear --enable-doc --htmldir=/usr/share/doc/ntpsec -v
>   ./waf build
>   ./waf install --destdir="$pkgdir/"
> 
> I get the following output in the failure:
> --- Configuring main ---
> Checking for endianness                   : 20:21:04 runner
> ['/usr/bin/gcc', '-std=c99', '-D_GNU_SOURCE', '-march=x86-64',
> '-mtune=generic', '-O2', '-pipe', '-fno-plt', '-fexceptions',
> '-Wp,-D_FORTIFY_SOURCE=3', '-Wformat', '-Werror=format-security',
> '-fstack-clash-protection', '-fcf-protection', '-fno-omit-frame-pointer',
> '-mno-omit-leaf-frame-pointer', '-flto=auto', '-DNTPSEC_VERSION="1.2.4"',
> '-DNTPSEC_VERSION_EXTENDED="1.2.4"', '../../test.c', '-c',
> '-o/home/gboyce/repo/ntpsec/src/ntpsec-1.2.4/build/.conf_check_c56fba856afc7
> 3ffddcea3140594c3eb/testbuild/main/test.c.1.o'] 20:21:04 runner
> ['/usr/bin/ar', 'rcs', 'libtestprog.a', 'test.c.1.o'] no
> The configuration failed
> (complete log in /home/gboyce/repo/ntpsec/src/ntpsec-1.2.4/build/config.log)
> ==> ERROR: A failure occurred in build().
>     Aborting...
> 
> I've attached config.log as well.
> 
> Oddly, if I add CFLAGS="-O2" before the waf configure line, it succeeds.

> I've been poking around waf a bit to try to better understand either issue,
> but so far I'm a bit stumped.
> 
> Do you have any suggestions?

Please see if you can drop "-flto=auto" from the list of CFLAGS

>>> Use -flto=auto to use GNU make's job server, if available,
>>> or otherwise fall back  to  autodetection  of  the number
>>> of CPU threads present in your system.

All the world does not revolve around make (not even GNU make).
We do not use make for instance which may cause brittle and/or
misconfigured meta-build systems to have issues.




More information about the users mailing list