severity 424038 important thanks On Sat, 19 May 2007, Roger Leigh wrote: > By removing the default, you are breaking software which used > "-lboost_program_options", which is going to break a lot of software. > It's also going to make it FTBFS in Debian. This applies equally to > all of the boost library packages with -mt and -st variants.
Roger is spot on here.. Just to add in my couple of cents worth.
As the boost library tranistion causes other packages in Debian to
FTBFS we need to ensure some level of coordination. At least I would
recommend that the boost team email the packages who have a rdepends
on boost libraries so we are at least aware of the issue, rather than
just stumbling across it the next time we try to build.
This change caused one of my packages, twinkle to FTBFS.
configure:20008: checking for main in -lboost_regex
configure:20037: g++ -o conftest -g -Wall -O2 -D_GNU_SOURCE
-DQT_THREAD_SUPPORT -D_REENTRANT conftest.cpp -lboost_regex -lzrtpcpp -lsp
eex -lasound -lsndfile -lresolv -L/usr/lib -lccext2 -lccgnu2 -lgnutls -lgcrypt
-lz -ldl -lrt -pthread >&5
/usr/bin/ld: cannot find -lboost_regex
collect2: ld returned 1 exit status
configure:20043: $? = 1
As my upstream is checking for -lboost_regex and I gather twinkle should now be
checking for -lboost_regex-{m,s}t.
My upstream does have a FAQ entry on this
<http://www.xs4all.nl/~mfnboer/twinkle/faq.html>, but suggests:
> Twinkle links to the libary libboost_regex.so On some systems the library is
> called libboost_regex-gcc.so To solve this problem you can make a symbolic
> link from libboost_regex-gcc.so to libboost_regex.so
Which is the simplest hotfix on single user machines, but not suitable
for a binary distribution.
For twinkle, I can change configure to check for -lboost_regex-mt, but only
now that I'm aware of the issue.
Mark
pgpnkrnQdxQ6u.pgp
Description: PGP signature
