Hello,
[Cc += sparse mailing list]
On Fri, Sep 14, 2018 at 05:04:09PM +0300, Adrian Bunk wrote:
> Control: reassign -1 sparse 0.5.2-1
> Control: affects -1 src:horst
>
> On Sat, Aug 25, 2018 at 10:09:47PM +0200, Christoph Biedl wrote:
> > Santiago Vila wrote...
> >
> > > make -j1 check
> > > make[1]: Entering directory '/<<PKGBUILDDIR>>'
> > > sparse -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -Wall -Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch]
> > > /usr/include/err.h:25:11: error: unable to open 'stdarg.h'
> >
> > To reproduce this it's important to remove gcc-7 from the build chroot
> > (apt purge libgcc-7-dev ; apt --purge autoremove).
> >
> > Problem is, sparse appearently uses hardcoded paths and looks for
> > stdarg.h in (among other places)
> >
> > | /usr/lib/gcc/x86_64-linux-gnu/7//include/stdarg.h
> > | ^
> >
> > ... which fails.
> >
> > Solution is to rebuild sparse, building horst was successful then.
> > If this is true (please check!), the interesting question is why this
> > wasn't a problem in earlier gcc version bumps.
I think this is a known limitation of sparse and there are three
ways to fix this (in my order of preference):
a) let horst use cgcc -no-compile instead of sparse; or
b) let sparse depend on libgcc-7-dev (or whatever provides the
necessary files); or
c) use autodetection which gcc is used and pick its files.
I'm not sure if a) fixes the problem. It fixed another problem we had
with horst's usage of sparse in the past though[1].
The downside of c) is that running this autodetection on every call to
sparse is probably slowing down sparse a bit which isn't nice.
Best regards
Uwe
[1] https://bugs.debian.org/873508
Attachment:
signature.asc
Description: PGP signature
