0c82598d22b69d8787faa1f9fe7c2e9bc62c4cfa upgraded the boost-build-native recipe to switch to 1.8x as this is required by the newer versions of boost. However this causes something curious to happen: When building boost for the target system, the b2 from boost-build-native takes the .jam files it installed to $sysroot-native/usr/share/b2 INSTEAD of the ones from the unpacked boost source I have cross-checked that as follows: - Backporting boost-build of least 1.79 to kirkstone. This breaks my patches for the python jam file similarly to master. 1.78 does not break it and the main difference is the install location of the jam files from boost-build-native - Moving /usr/share/b2 to /usr/share/boost-build (default before before 1.79) restores the old behavior. I am happy to provide a fix, but I have no idea what the expected behavior here is. Mine would be that patching the build files of the target should have an effect.
Hi Jens, No one in the Yocto triage call has any experience with that so could you post a patch to the list? Welcome to Yocto from a former physics geek (LBL, JLab!) -- Randy
Naively poking around a bit, seems this might be related? https://github.com/boostorg/build/blob/develop/doc/src/history.adoc#version-490 Warning This release removes the use of boost-build.jam and the boost-build rule for initialization. The boost-build.jam is still searched for and loaded to not break existing operations. But is considered deprecated and will be removed in a future release.
Apparently upstream is transitioning to https://github.com/bfgroup/b2 This commit is slightly concerning: https://github.com/bfgroup/b2/commit/e746a952c7a350acf4884454022e0d9bac8c4dd5 Remove Python port. The Python port and support extensions in B2 engine were unmaintained. This fully removes the bindings between Jam and Python. And removes the incomplete build system port.
(In reply to comment #3) > Apparently upstream is transitioning to https://github.com/bfgroup/b2 The boost build systems utterly confuse me. I though boost-build was the externalized version of what is bootstrapped inside boost (In reply to comment #3) > Remove Python port. > The Python port and support extensions in B2 engine were unmaintained. > This fully removes the bindings between Jam and Python. And removes the > incomplete build system port. I think the python port only references the port of the build system to python?
Sow e agree that modifying boosts build files in a recipe should be possible? If so, I will dig into this and try to come up with a solution
Moved en masse from 4.2 to 4.3 by Randy.
Do you still plan to look into this Jens?
Sort of related: in case anyone is interested, I've started on a b2 5.0 recipe in poky-contrib:ross/b2. I don't know if that will solve this problem...
Hi, sorry, this toppled down in priority on our side, the current plan was to get back onto Yocto topics in two weeks and start looking into this.
The b2 5.0 package from Ross shows the same behavior, unfortunately
Furthermore, while it is possible to use b2 5.0 to compile boost, it is not possible to use the b2 core inside boost then, because its too old. I am now somewhat leaning forward that one needs to be aware that patches have to go to the build tool not boost, however unfortunate and backwards-seeming that is, because python.jam is actually part of the build tool, not boost.
Bulk move of 5.1 bugs to 5.2. -- YP bug review (Randy)
In my opinion this is obsolete. Misunderstanding caused by a bug in the boost recipies that was actually fixed with 0c82598d22b69d8787faa1f9fe7c2e9bc62c4cfa
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15031#c13