boost.python from boost-1.48 breaks compilation of paludis. Reproducible: Always
Created attachment 300189 [details] build.log This is the log for paludis-0.70.2. I copied the ebuild from 0.70.1, as I thought 0.70.2 (not yet in portage) could fix this issue, but it failed with exactly the same error as 0.70.1 did.
Created attachment 300247 [details] Patch that adds $PATHON_VERSION to boost_python in configure I know, this is not that great - a patch that needs to be applied occasionally. But I don't have the skills/time to modify configure so that it takes the boost-version from boost/version.hpp and sets boost_python-name as needed. I just wanted to get paludis build with python-bindings and boost-1.48...
I suggest to implement --with-boost-python=argument option, which would be passed by ebuild.
Created attachment 300319 [details, diff] 0001-Support-new-Gentoo-boost.python-library-names.patch (In reply to comment #3) > I suggest to implement --with-boost-python=argument option, which would be > passed by ebuild. The attached patch makes configure support the new naming scheme directly. I didn't use an option because doing it this way 1) guarantees that configure will look for a boost.python library matching the same version of Python that it found, which might not necessarily be the same as what the ebuild thinks it'll be, and 2) means I won't have to worry about this for my own development builds. I can add the option as well though, if there's still a use for it. This will be pushed upstream if no-one asks for the configure option soon (it can still be added later if necessary of course), and can probably be applied to previous versions as well if required.
sys-apps/paludis-0.72.0 is now gentoo-x86 and is supposed to contain the fix.
This is now fixed in 0.72.0