id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,irc_client,os,os_version 786,Build system doesn't differentiate between compiler and linker options,stefanor@…,,"Bitlbee's build system mixes compiler and linker options. Debian and Ubuntu are trying to enforce stricter linking behavior, to ease the transition to the gold linker: http://wiki.debian.org/ToolChain/DSOLinking One of the issues encountered was that bitlbee's otr plugin wasn't linked against libotr2, resulting in https://bugs.launchpad.net/ubuntu/+source/bitlbee/+bug/757008 I think this happened because -lotr came before gcc arguments (-fPIC and the .c file). Linker arguments must come last: {{{$ gcc -g -O2 -I/home/stefanor/deb/bitlbee-3.0.1/debian/build-native -I/home/stefanor/deb/bitlbee-3.0.1 -I/home/stefanor/deb/bitlbee-3.0.1/lib -I/home/stefanor/deb/bitlbee-3.0.1/protocols -I. -DHAVE_CONFIG_H -Wall -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include -I/usr/include -MD -MF .depend/otr.so.d -L/usr/lib -lotr -fPIC -shared /home/stefanor/deb/bitlbee-3.0.1/otr.c -o otr.so}}} Additionally, it would be really handy if the build system outputted the commands it was running.",defect,new,normal,,BitlBee,3.0.2,,,,Client-independent,Linux,