On Mon, 2013-10-21 at 12:44 +0200, Ivo De Decker wrote: > Andrew, > > On Mon, Oct 21, 2013 at 11:32:14PM +1300, Andrew Bartlett wrote: > > > cups-config --libs: > > > -lcups -Wl,-z,relro -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls > > > -lgcrypt -lz -lpthread -lm -lcrypt -lz > > > > > > cups-config --ldflags > > > -L/usr/lib/x86_64-linux-gnu > > > > The patch will need to be to source3/wscript where it calls cups-config, > > or in buildtools/wafadmin/Tools/config_c.py:parse_flags(). One way or > > the other, I don't think we should not put the default linker path in > > there at all. > > When -L/usr/lib/x86_64-linux-gnu is listed after > -L/usr/lib/x86_64-linux-gnu/heimdal, it seems to work, but it would be very > fragile to rely on that. > > Where exactly is the order of the ldflags decided in the waf code?
G'Day, We just had this come up in another context, where the -L was instead an -rpath directive on FreeBSD. I've CC'ed Volker and Michael who dealt with that. I think we probably should forcibly remove the default search path from the flags we honour. We already ignore the --libs output, and ordering in waf is a difficult art. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
