linux/poky.git/meta/recipes-support/boost/files, branch hardknott

bjam-native: don't do debug builds

2020-10-06T22:14:24+00:00

Previously this recipe was changed to do debug builds because otherwise insane warns that the binary is already stripped. However, debug builds for boost.build also pass -O0. It turns out that given how large Boost is (or, how bad boost.build is) doing a release build with -O3 knocks a third off the walltime for a Boost package in my test, mainly by reducing how long it spends deciding that nothing needs to be rebuilt in do_install: PKG TASK ABSDIFF RELDIFF WALLTIME1 -> WALLTIME2 boost do_install -330.7s -69.2% 477.6s -> 146.9s boost do_compile -7.1s -2.7% 269.3s -> 262.2s Replace debug mode with INSANE_SKIP=already-stripped. (From OE-Core rev: 66d583d1b2bc54cac278c30b5dbc9fde016eb6ee) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boost: upgrade 1.72.0 -> 1.73.0

2020-05-24T22:56:03+00:00

refresh 0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch remove 0001-revert-cease-dependence-on-range.patch since it is included in 1.73.0 (From OE-Core rev: 1728ecf71f96570913202a54fd0012ac8b01b8ae) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie

boost: revert 1.72.0 regression

2020-04-26T13:00:49+00:00

https://www.boost.org/users/history/version_1_72_0.html documents a "Known Issue" and has a revert patch for an issue that causes code to fail to compile that includes the coroutine function. Without this patch, code which includes the asymmetric_coroutine.hpp will fail to compile. (From OE-Core rev: e25e3f151c324272990ad6370c5bc71fd5d05c8c) Signed-off-by: Andrew Geissler Signed-off-by: Richard Purdie

boost: update to 1.71.0

2019-08-28T10:31:21+00:00

Some notes: - bjam bootstrap scripts were changed, and the patch for that had to be adjusted. tools/build/src/engine/build.sh now supports an --debug option which the bjam-native recipe can use to get the debug build of b2. - a related patch was added to address a speed regression with the debug version of bjam - gcc.jam patch had to be refreshed because boost added more "cpu-flags" lines. - since 1.70.0, boost includes new cmake config files which are packaged in ${PN}-dev now so they make it into the SDK. (although 1.71.0 is needed to fix some bugs in them) (From OE-Core rev: 810aded01fc2ae2c27c2573135c20947453e50c6) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

boost: update to 1.67.0

2018-05-04T12:28:05+00:00

* Remove the backported patch 0001-Fix-a-strange-assert-typo-how-was-this-released-with.patch * Remove the patch 0002-Don-t-set-up-m32-m64-we-do-that-ourselves.patch as it already rewritten gcc to use toolset.flags again as below: commit 12decb3ce680031b915f69902795eec47224fc7d Author: Steven Watanabe Date: Mon Jan 1 12:51:43 2018 -0700 Rewrite gcc to use toolset.flags again. * Remove the hardcoded parallel build limit as the mechanism already changed as below commit: commit 316e26ca718afc65d6170029284521392524e4f8 Author: Steven Watanabe Date: Wed Apr 26 14:22:06 2017 -0600 Remove fixed limit to -j. Fixes #189. * execunix.c: Replace select with poll. * execnt.c: Use RegisterWaitForSingleObject when the number of jobs exceeds MAXIMUM_WAIT_OBJECTS. Reference: https://github.com/boostorg/build/commit/316e26ca718afc65d6170029284521392524e4f8#diff-c88fe8afebc632d0bef2bd5985137af2 (From OE-Core rev: 358cf46ea4d01b7ad8c355fa103d4a6922cc0a88) Signed-off-by: Mingli Yu Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boost: update to 1.65.1

2017-11-09T12:33:16+00:00

Add a patch to fix bjam-native compile error (due to mistyped variable name). Drop upstreamed patch. (From OE-Core rev: ba2d391d8268203895ab2f792f92b7fd92deeb45) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

boost: update to 1.60.0

2016-01-11T23:26:30+00:00

Due to the version update to 1.59.0, the two patches previously backported in this recipe are now dropped. The actual status of the arm-intrinsics.patch (reported with Upstream-Status: Backport) is unknown to the committer, and hence, that patch is kept in the recipe, even if it is possibly not required anymore. A deeper analysis is required to determine need and status of that patch. Second, boost 1.59.0 provides a new library, called timer, which is packaged as further library in the boost recipe. The update to boost 1.60.0 required no further changes beyond changing the checksum hashes. Third, on PPC architectures, qemuppc & mpc8315e-rdb [1] (tested by Ross Burton), the boost test library with the vanilla version 1.60.0 fails with: | gcc.compile.c++ bin.v2/libs/test/build/aca09349fdb84d131321425f6c3a38ed/execution_monitor.o | In file included from [...]/tmp/sysroots/mpc8315e-rdb/usr/include/fenv.h:114:0, | from [...]/tmp/sysroots/mpc8315e-rdb/usr/include/c++/5.3.0/fenv.h:36, | from ./boost/detail/fenv.hpp:97, | from ./boost/test/execution_monitor.hpp:64, | from ./boost/test/impl/execution_monitor.ipp:31, | from libs/test/src/execution_monitor.cpp:16: | ./boost/test/impl/execution_monitor.ipp: In function 'unsigned int boost::fpe::enable(unsigned int)': | ./boost/test/impl/execution_monitor.ipp:1383:7: error: expected id-expression before '(' token | ::feclearexcept(BOOST_FPE_ALL); | ^ | ./boost/test/impl/execution_monitor.ipp: In function 'unsigned int boost::fpe::disable(unsigned int)': | ./boost/test/impl/execution_monitor.ipp:1420:7: error: expected id-expression before '(' token | ::feclearexcept(BOOST_FPE_ALL); | ^ The commit f50e7bc9fed323c5705c0ed992c03e80eeec1dd6 from the boostorg/test github repository (branch: develop) [2] addresses that issue, but it was not merged in the 1.60.0 release. This commit adds this upstream-accepted patch, which was created by: `git checkout f50e7bc9fed323c5705c0ed992c03e80eeec1dd6 && git format-patch -1` [1] http://lists.openembedded.org/pipermail/openembedded-core/2016-January/114844.html [2] https://github.com/boostorg/test/commit/f50e7bc9fed323c5705c0ed992c03e80eeec1dd6 (From OE-Core rev: 17d77db5e1203e18cdd178e7d9a457310425ebdc) Signed-off-by: Lukas Bulwahn Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bjam-native: build and install bjam.debug

2015-09-12T21:48:36+00:00

bjam is stripped by default, this causes QA warning while stripping it from do_populate_sysroot(): WARNING: File '.../tmp/sysroots/x86_64-linux/usr/bin/bjam' \ from bjam-native was already stripped, \ this will prevent future debugging! The JAM scripts allow to build unstripped version with '--debug'. Just build and install the bjam.debug to stop bjam from being stripped in compile step. (From OE-Core rev: e7147de9f28925b1bb5df39d9c0848dd7957328c) Signed-off-by: Wenzong Fan Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boost: fix build for mips

2015-06-03T15:38:45+00:00

Backport 2 patches to fix the build error on mips: mips-poky-linux-g++: error: unrecognized command line option '-m32' https://github.com/boostorg/build/commit/c0634341d9ee2c02d3a55c91dafb988afc066c49 https://github.com/boostorg/build/commit/9576ca216cae888d7efb5da97c009c245c5ba567 Apply the pacthes to both bjam-native and boost, so put the patches to "files" dir. (From OE-Core rev: 729592223a0c076abe2c58a0cf3f4c6d6583602c) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

boost: Move files -> boost

2013-12-09T18:01:45+00:00

(From OE-Core rev: aca3d0bfd8335b7fd293d81c0647bf72b4de23d3) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie