It seems the dev-libs/boost-1.33.1 does not properly install files necessary to build boost.python modules. For example: in BOOST_SRC/libs/python/example/ one must edit Jamrules so that: path-global BOOST_ROOT : /usr/include ; one must edit boost-build.jam so that: boost-build /usr/share/boost-build/v1 ; Then running $ bjam test1 ... the build succeeds, but the module does not import because it is not linked to libboost_python.so The reason for this is can be seen in the report of two missing files: /usr/include/Jamrules: No such file or directory /usr/include/libs/python/build/Jamfile: No such file or directory These two files are in BOOST_SRC/ thus the /usr/includes/boost is insufficent to build boost.python modules. Additional files need to be installed, perhaps to a new dir such as /usr/share/boost-root. If then also the include files where put there under /usr/share/boost-root/boost, then one must edit Jamrules so that: path-global BOOST_ROOT : /usr/share/boost-root ; This should fix the problem.
I too am having this problem but do not fully understand your fix. The sentence: "Additional files need to be installed" ./libs/python/build/Jamfile is included in the boost tarball, but not currently installed by the ebuild. I agree that it could be put somewhere like /usr/share/boost-root. However, which file is it looking for when it attempts to access /usr/include/Jamrules? The Jamrules for the current project? The Jamrules in the root of the boost tarball? Or something completely different? "If then also the include files where put there under" I would assume this could be symlinked.
Ok. Let's see if I understood the problem correctly: You're trying to compile the python-examples in the boost-package, right? Because there are actually ebuilds in portage, which use boost.python and they work without adding files. As far as I can see, the examples are meant to be built using boost as it is in the tarball. So, please try to set BOOST_ROOT to BOOST_SRC and see if it works. . boost-build can point to /usr/share/boost-build/v1, that should be ok.
Closing this bug since I really don't think it's a problem we could/should/have to fix (see comments above). If you don't agree, please reopen or contact me.
