On 1 August 2024 at 13:11, Santiago Vila wrote:
| Package: src:sprng
| Version: 2.0a-14
| Severity: serious
| Tags: ftbfs patch
| 
| Dear maintainer:
| 
| The current package FTBFS in trixie:
| 
| 
https://tests.reproducible-builds.org/debian/rbuild/trixie/amd64/sprng_2.0a-14.rbuild.log.gz
| 
| make[4]: Entering directory '/build/reproducible-path/sprng-2.0a/SRC'
| gcc-14 -c -O -fpic -DUSE_PMLCG   -O2 -D_REENTRANT primes_32.c
| make[4]: gcc-14: No such file or directory
| make[4]: *** [Makefile:50: primes_32.o] Error 127
| make[4]: Leaving directory '/build/reproducible-path/sprng-2.0a/SRC'
| make[3]: *** [Makefile:37: sprng] Error 2
| make[3]: Leaving directory '/build/reproducible-path/sprng-2.0a/SRC/sprng'
| make[2]: *** [Makefile:32: all] Error 2
| make[2]: Leaving directory '/build/reproducible-path/sprng-2.0a/SRC'
| make[1]: *** [Makefile:36: src] Error 2
| make[1]: Leaving directory '/build/reproducible-path/sprng-2.0a'
| dh_auto_build: error: make -j42 src returned exit code 2
| make: *** [debian/rules:37: build-stamp] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
| 
| This happens because several Makefiles have CC=gcc-14.
| (If we do that, we would have to build-depend on gcc-14, because
| gcc is essential but gcc-14 is not).
| 
| The attached trivial patch (which I've tested in trixie)
| should fix this.
| 
| [ Please note that the patch is against the current version in unstable.
| The version in salsa has "aggregated_patches" in debian/patches
| but a "series" file which does not reference it. ]

Yes yes yes. I was fighting with quilt and debian/patches here and was unable
to cleanly add more patches (which works in other packages of mine) so the
gcc-14 was an accidental by-product of syncing once more with my 'test
directory' where I checked with gcc-14.

I will clean this up, and the patch is helpful and obvious.

Thanks for noticing and the help (and added testing). I really appreciate it.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Reply via email to