Summary: | dev-util/monotone-0.33 & 0.35 fails configure with dev-utils/boost-1.34.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Xake <kanelxake> |
Component: | New packages | Assignee: | Daniel Black (RETIRED) <dragonheart> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | dschridde+gentoobugs, johnny, tetromino |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
config.log from monotone
boost-1.34.0.ebuild that builds debug and release |
Description
Xake
2007-06-21 23:02:27 UTC
I cannot confirm this. Using dev-libs/boost-1.34.0 and dev-util/monotone-0.35: checking boost version 1.32.0 or newer... yes checking for the boost_filesystem library... yes checking for the boost_regex library... yes checking for the boost_unit_test_framework library... no Maybe gcc-4.2 is to blame? What does the config.log say? Created attachment 124368 [details]
config.log from monotone
"gcc-config i686-pc-linux-gnu-4.1.2 && source /etc/profile && emerge boost-build boost monotone -1" fails in the same way.
$ find /usr/lib | grep boost_filesystem
/usr/lib/libboost_filesystem-mt-sd.a
/usr/lib/debug/usr/lib/libboost_filesystem-mt-d.so.debug
/usr/lib/debug/usr/lib/libboost_filesystem-d.so.debug
/usr/lib/libboost_filesystem-sd.a
/usr/lib/libboost_filesystem-d.so
/usr/lib/libboost_filesystem-mt-d.so
The config.log attached is from that try. I am going to poke around a bit in this when I come home again (sometime next week).
Created attachment 124451 [details]
boost-1.34.0.ebuild that builds debug and release
This is a bug (or misfeature) in the boost-1.34.0 ebuild.
Boost libraries come in two versions: debug and release. The libraries have different names (the debug versions have a "d" suffix), and many applications that use boost, such as monotone, expect to link against the release version. Now, when USE="-debug", the existing ebuild builds only the release version (good). When USE="debug", it builds only the debug version (not good, breaks stuff).
Therefore, I've attached a new boost ebuild that builds both release and debug versions when USE=debug.
Tiziano - take a look at Alex's ebuild. Looks a touch neater than symlinking libs. Your call as always :-). *** This bug has been marked as a duplicate of bug 181972 *** Didn't really try it but I guess that it takes again twice the time to build boost, even for people not interested in the debugging stuff. And we already build twice: Once for multithreading and once without. So, symlinking the stuff for the people really wanting to debug seems to be the better solution for now. (In reply to comment #5) > Didn't really try it but I guess that it takes again twice the time to build > boost, even for people not interested in the debugging stuff. > And we already build twice: Once for multithreading and once without. > So, symlinking the stuff for the people really wanting to debug seems to be the > better solution for now. Please try it before criticizing. Or at least read the ebuild. It only builds twice for people who have USE=debug. |