On Fri, Sep 04, 2015 at 08:33:52PM +0200, Jakub Wilk wrote: > "help" is not a helpful subject. I updated it, so that is provides some > context. :)
> If you want people to help you, you need to make it easy for them to > understand and reproduce the problem. In case of compiler errors, including > the compiler command that failed is absolute minimum. Especially for this one, the common problem here is that the order of options is wrong. e.g. ld thing.o -lqdb -lthingqbneeds So if libqdb needs symbols from libthingqdbneeds it will error like this. Sometimes the dpkg-buildflags (correctly) trips these things up. I've found them a useful check for getting upstream in order. But yes, as Jakub said, bit hard to debug this further without the actual command line. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
