On my mac running OS X 10.5.8 boost-1.49 built with the python useflag only produces libboost_python-2.7-mt.dylib on a regular gentoo install I also have libboost_python-2.7.so - so I am expecting the dylib equivalent. I noticed this because an ebuild in the sage-on-gentoo overlay of which I am a maintainer is depending on this library. On a regular gentoo install, they have the same size and while diff say they differ they may be effectively identical.
*-mt-* libraries are built with multithreading enabled. They are additionally linked against e.g. librt.so.1. $ scanelf -qF "%F: %n" /usr/lib64/libboost_python-2.7*1_49.so /usr/lib64/libboost_python-2.7-1_49.so: libutil.so.1,libpython2.7.so.1.0,libpthread.so.0,libdl.so.2,libstdc++.so.6,libgcc_s.so.1,libc.so.6 /usr/lib64/libboost_python-2.7-mt-1_49.so: libutil.so.1,libpython2.7.so.1.0,libpthread.so.0,libdl.so.2,librt.so.1,libstdc++.so.6,libgcc_s.so.1,libc.so.6
I'm affraid on Darwin this makes no difference, as there is no librt. It seems 1.46 *did* build the non"-mt-" versions, whereas 1.49 does not.
These non"-mt-" versions of boost-1.49 are also missing on my amd64-linux and x86-linux machines.
Any solution around?
adding us back
I'd call this fixed by the fact that now threads USE flag decides whether to have them multithread or not (by default they are) and the -mt stuff is only compatibility symlinks.
