On Wed, Mar 7, 2012 at 2:20 PM, Ionut Biru <ibiru@xxxxxxxxxxxxx> wrote: > On 03/07/2012 10:16 PM, Ionut Biru wrote: >> On 03/07/2012 09:52 PM, David C. Rankin wrote: >>> Guys, >>> >>> Ran into a big problem with sane 1.0.22-6 causing builds to fail due to the >>> return of 'sane-config --libs' returning non-library flags which results in >>> CMake botching the link config. From the sane-config man page: >>> >>> --libs Print the additional libraries that are necessary to link a SANE >>> frontend to libsane. >>> >>> Currently, on arch, 'sane-config --libs' returns: >>> >>> 10:51 providence:~/bld/david> sane-config --libs >>> -lsane -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -L/usr/lib >>> -lnetsnmp -lcrypto -lm -ldl -lv4l1 -lm -ltiff -ljpeg -lgphoto2 -lgphoto2_port >>> -lm -lexif -lusb -lavahi-common -lavahi-client -lusb >>> >> >> You should open a bug report than sending this on mailing list. >> > > > the idea is that net-snmp includes wrong stuff into libs and that's why > they ended up in sane > > $ net-snmp-config --libs > > -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -L/usr/lib > -lnetsnmp -lcrypto -lm These are all linker flags and should be ok to use in --libs. The issue is the incorrect concatenation in the final link line.
