On 15/02/2019 21:28, Uwe Kleine-König wrote: [snip] >>> Right. The problem was https://bugs.debian.org/906472 . >> >> Oh, my word! So, the 'horst' package was using sparse on user-space >> code directly, not via 'cgcc -no-compile'? I am somewhat surprised >> that it worked at all! ;-) >> >> Also, it seems that the package was built in a chroot environment >> where the compiler was 'swapped out' mid build! What ??? No, no I >> must have misunderstood something. :( > > There happened nothing in the middle of the build. > > sparse 0.5.2-1 was built in April 2018 when gcc was still gcc-7, so it > used the gcc-7 path. Later in August after gcc was bumped to gcc-8 to > build horst the following packages were installed: > > sparse 0.5.2-1 > gcc-8 > > and no gcc-7. As sparse was not rebuild from source but just the binary > from April installed sparse failed to find stdarg.h. Ah, yes, that makes sense. So, had the 'horst' Makefile used 'cgcc -no-compile', then it would likely have worked. (cgcc would have called 'gcc -print-file-name=', which would have passed the gcc-8 path to sparse). ATB, Ramsay Jones
