Configure script fails to find installed boost. As far as I understood the is with autoconf. Upgrading autoconf to 2.65 gave nothing. At first I tried standard Gentoo-provided net-libs/rb_libtorrent-0.14.6 ebuild See build1.log, config1.log for details. Configure does not find boost libs though they are definitively installed. Then I tried patch from http://bugs.gentoo.org/show_bug.cgi?id=295474 now I saw another error. See build2.log, config2.log Reproducible: Always
Created attachment 216394 [details] Build log for Portage-tree version
Created attachment 216395 [details] Configure log for Portage-tree version
Created attachment 216396 [details] Build log for patched version
Created attachment 216397 [details] Configure log for patched version
Created attachment 216400 [details] Paludis info
Try 'eselect boost' first to create the correct symlinks.
I tried eselecting 1.41 version, but with no luck. I think ebuild should choose latest or predefined boost version by itself.
Define "no luck". Right now it's transition period, as older versions of boost were not handled by eselect. What does 'ls -l /usr/lib/libboost_system*' print ?
A root of this bug appears to be the boost autoconf macros in autoconf-archive, which rb_libtorrent's upstream uses, are incompatible with the Gentoo boost installation. Bug 300653 seems to have good discussion about this type of issue too.
(In reply to comment #8) > Define "no luck". > Right now it's transition period, as older versions of > boost were not handled by eselect. > What does 'ls -l /usr/lib/libboost_system*' print ? > I mean nothing actually changes. Configure still unable to find boost. -rw-r--r-- 1 root root 16444 Янв 12 19:24 /usr/lib/libboost_system-1_35.a lrwxrwxrwx 1 root root 30 Янв 12 19:24 /usr/lib/libboost_system-1_35.so -> libboost_system-1_35.so.1.35.0 -rwxr-xr-x 1 root root 13796 Янв 12 19:24 /usr/lib/libboost_system-1_35.so.1.35.0 -rw-rw-r-- 1 root root 16300 Июн 19 2009 /usr/lib/libboost_system-1_37.a lrwxrwxrwx 1 root root 30 Сен 13 19:05 /usr/lib/libboost_system-1_37.so -> libboost_system-1_37.so.1.37.0 -rwxrwxr-x 1 root root 13860 Июн 19 2009 /usr/lib/libboost_system-1_37.so.1.37.0 -rw-r--r-- 1 root root 16300 Янв 12 20:40 /usr/lib/libboost_system-1_39.a lrwxrwxrwx 1 root root 30 Янв 12 20:40 /usr/lib/libboost_system-1_39.so -> libboost_system-1_39.so.1.39.0 -rwxr-xr-x 1 root root 13796 Янв 12 20:40 /usr/lib/libboost_system-1_39.so.1.39.0 -rw-r--r-- 1 root root 14634 Янв 12 22:48 /usr/lib/libboost_system-1_41.a lrwxrwxrwx 1 root root 30 Янв 12 22:48 /usr/lib/libboost_system-1_41.so -> libboost_system-1_41.so.1.41.0 -rwxr-xr-x 1 root root 13796 Янв 12 22:48 /usr/lib/libboost_system-1_41.so.1.41.0 -rw-r--r-- 1 root root 16444 Янв 12 19:24 /usr/lib/libboost_system-mt-1_35.a lrwxrwxrwx 1 root root 33 Янв 12 19:24 /usr/lib/libboost_system-mt-1_35.so -> libboost_system-mt-1_35.so.1.35.0 -rwxr-xr-x 1 root root 13796 Янв 12 19:24 /usr/lib/libboost_system-mt-1_35.so.1.35.0 -rw-rw-r-- 1 root root 16300 Июн 19 2009 /usr/lib/libboost_system-mt-1_37.a lrwxrwxrwx 1 root root 33 Сен 13 19:05 /usr/lib/libboost_system-mt-1_37.so -> libboost_system-mt-1_37.so.1.37.0 -rwxrwxr-x 1 root root 13860 Июн 19 2009 /usr/lib/libboost_system-mt-1_37.so.1.37.0 -rw-r--r-- 1 root root 16300 Янв 12 20:40 /usr/lib/libboost_system-mt-1_39.a lrwxrwxrwx 1 root root 33 Янв 12 20:40 /usr/lib/libboost_system-mt-1_39.so -> libboost_system-mt-1_39.so.1.39.0 -rwxr-xr-x 1 root root 13796 Янв 12 20:40 /usr/lib/libboost_system-mt-1_39.so.1.39.0 -rw-r--r-- 1 root root 14634 Янв 12 22:48 /usr/lib/libboost_system-mt-1_41.a lrwxrwxrwx 1 root root 33 Янв 12 22:48 /usr/lib/libboost_system-mt-1_41.so -> libboost_system-mt-1_41.so.1.41.0 -rwxr-xr-x 1 root root 13796 Янв 12 22:48 /usr/lib/libboost_system-mt-1_41.so.1.41.0 -rw-r--r-- 1 root root 16444 Янв 12 19:24 /usr/lib/libboost_system-mt-s-1_35.a -rw-rw-r-- 1 root root 16300 Июн 19 2009 /usr/lib/libboost_system-mt-s-1_37.a -rw-r--r-- 1 root root 16444 Янв 12 19:24 /usr/lib/libboost_system-s-1_35.a -rw-rw-r-- 1 root root 16300 Июн 19 2009 /usr/lib/libboost_system-s-1_37.a
(In reply to comment #9) > A root of this bug appears to be the boost autoconf macros in autoconf-archive, > which rb_libtorrent's upstream uses, are incompatible with the Gentoo boost > installation. > > Bug 300653 seems to have good discussion about this type of issue too. > I agree with you. One can notice that when using ebuild patch config2.log shows that configure script tries to find version.hpp in the wrong directory. I think that's why it fails.
(In reply to comment #6) > Try 'eselect boost' first to create the correct symlinks. It has nothing to do with eselect boost, as ebuilds always have to use the latest installed version. The eselect boost mechanism is purely for the user and not to be used by portage.
*** This bug has been marked as a duplicate of bug 295474 ***
