On Mon, Sep 08, 2014 at 10:07:38PM -0700, Russ Allbery wrote: > James McCoy <james...@debian.org> writes: > > On Tue, Sep 09, 2014 at 12:48:11AM -0400, Benjamin Kaduk wrote: > > >> krb5 has started supplying pkgconfig files in 1.12; would it be easier for > >> serf to use gssapi.pc instead of parsing krb5-config's output? > > > No, since the issue is the lack of understanding of the -isystem flag, > > which is still going to be emitted by pkg-config, twice in fact: > > > $ pkg-config --cflags krb5-gssapi > > -isystem /usr/include/mit-krb5 -isystem /usr/include/mit-krb5 > > I suspect Ben's hope was that, if using pkgconfig, scons would not make an > attempt to parse the flags and split them apart, and would instead just > use them as-is in the compiler invocation. > > I must say that I've come to consider build systems that think they know > more than I do about what compiler flags mean to be a latent bug. Libtool > has had no ends of problems and irritating behavior because it likes to > think that it knows what all the compiler and linker flags are and how to > rearrange them. Given that one of scons's goals was to be simpler and > more predictable than the Autotools, it's unfortunate it fell into the > same trap in this specific instance. (That said, this is also partly > pkgconfig's fault for not separating CFLAGS and CPPFLAGS.)
One workaround might be to include an equals sign in between -isystem and the path to prevent scons from splitting it. gcc, tcc and clang all seem happy with this. I'll do some more tests this week to see if that works with serf. Cheers, Jelmer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
