Summary: | dev-libs/boost-1.37.0 creates bad symlinks | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Adam Nielsen <a.nielsen> |
Component: | New packages | Assignee: | Tiziano Müller (RETIRED) <dev-zero> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cpp+disabled |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Adam Nielsen
2009-01-28 21:43:49 UTC
Can you please tell me which versions of boost-build you have installed? Do you have any other versions of boost installed (like dev-libs/boost-1.36.0)? Are the ebuilds from my overlay or from the official gentoo tree? Adam, are you building boost with USE=debug maybe? Yes, you're right! I was building with 'debug' - is that a bad idea? I tried rebuilding without debug and all the symlinks are correct. I'm building with boost-build-1.37.0, and Portage automatically uninstalled the previous version I had which was 1.35. This is all from the official Gentoo tree. (In reply to comment #3) > Yes, you're right! I was building with 'debug' - is that a bad idea? I tried > rebuilding without debug and all the symlinks are correct. I got the broken symlinks, while USE="-debug" for boost from the beginning. [ebuild R ] dev-util/boost-build-1.37.0 USE="python -examples" 0 kB [ebuild R ] dev-libs/boost-1.37.0-r1 USE="eselect expat icu python -debug -doc -mpi -tools" the broken symlinks for: USE="-debug" emerge boost ls -l /usr/lib64/libboost_thread-1_37-debug.* lrwxrwxrwx 1 root root 31 2009-04-08 08:40 /usr/lib64/libboost_thread-1_37-debug.a -> libboost_thread-mt-1_37-debug.a lrwxrwxrwx 1 root root 32 2009-04-08 08:40 /usr/lib64/libboost_thread-1_37-debug.so -> libboost_thread-mt-1_37-debug.so Are you sure those symlinks aren't left over from a previous Boost install? I don't have those debug libraries: $ ls -l /usr/lib64/libboost_thread-1_37* lrwxrwxrwx 1 root root 25 2009-01-30 22:53 /usr/lib64/libboost_thread-1_37.a -> libboost_thread-mt-1_37.a lrwxrwxrwx 1 root root 26 2009-01-30 22:53 /usr/lib64/libboost_thread-1_37.so -> libboost_thread-mt-1_37.so I'm still not sure why the "debug" USE flag would completely break everything though... (In reply to comment #6) > Are you sure those symlinks aren't left over from a previous Boost install? I > don't have those debug libraries: yes, I first "emerge -C boost", the links were gone. "emerge boost" brings them back. also, $ qlist boost|grep debug /usr/lib64/libboost_thread-1_37-debug.so /usr/lib64/libboost_thread-1_37-debug.a emerge -pv boost [ebuild R ] dev-libs/boost-1.37.0-r1 USE="eselect expat icu python -debug -doc -mpi -tools" 0 kB For me, I had boost-1.35.0-r2 and attempted to upgrade to boost-1.37.0-r1. Portage complained about a blocking condition and said it was uninstalling 1.35 before installing 1.37. After the 1.37 install I noticed that /usr/include and /usr/lib had all kinds of broken symlinks from the 1.35 rev. I had to remove all boost installations and then clean up all broken symlinks before re-emerging 1.37. That was a bug in the part creating the symlinks. That should be solved by now. |