The boost ebuild installs the Boost.Build system into /usr/share/boost. Unfortunately, though, it does not install the bjam utility which you need to run the build system! bjam is a separate package, but that package installs a version of bjam that is too old to actually run the build system. So the macro packages installed in /usr/share/boost are, essentially, unusable in Gentoo. My recommendation would be to (a) install bjam along with the build macros when compiling boost, or to (b) build bjam from the boost sources, not from the (oooold) bjam release that's available for download separately. Last but not least, bjam searches the macro packages at the path: /usr/share/boost-build So it might be wise to rename the directory accordingly. Reproducible: Always Steps to Reproduce: 1. 2. 3.
ok, this will be with a USE=bjam when im done, and since you already about my off time, no second dose of boring you wiht it ;)
*** Bug 91337 has been marked as a duplicate of this bug. ***
Has there been any progress on that issue?
been side tracked majorly by a still unresolved issue with glibc on ppc (+nptl -nptlonly creates a unusable system) i have not forgotten about all boost feature requests/bugs
My apologies for the long delay, can you sync in one hour and try the masked 1.33.0-r1 ebuild, i would appreciate your feedback, especially since i never used bjam for anything but building boost itself. USE=bjam to have bjam installed if you are interested you can try USE=bcp as well hope this works as you would expect it Daniel P.S. do you have/use icc?
With the positive feedback i have gotten so far i think it is safe to close this bug. Thank you for your interest.
