@@ -7,7 +7,8 @@ LICENSE = "BSL-1.0"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=e4224ccaecb14d942c71d31bef20d78c"
SRC_URI = "git://github.com/boostorg/build;protocol=https;branch=master;tag=boost-${PV} \
- file://add-python-numpy-include-feature.patch"
+ file://add-python-numpy-include-feature.patch \
+ file://python-glibc.patch"
SRCREV = "05b6b638b54e1f013fb8b281f5020e337be31363"
PE = "1"
new file mode 100644
@@ -0,0 +1,19 @@
+Calling ldd on the host glibc to make decisions about the target isn't cross compile
+safe, don't do it. We always have a new enough tagret glibc so we can skip this test.
+
+Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
+
+Upstream-Status: Inappropriate [Upstream would need a proper fix rather than a workaround]
+
+Index: boost-build-1.92.0/src/tools/python.jam
+===================================================================
+--- boost-build-1.92.0.orig/src/tools/python.jam
++++ boost-build-1.92.0/src/tools/python.jam
+@@ -624,6 +624,7 @@ local rule candidate-interpreters ( vers
+ local rule gcc-use-libutil ( )
+ {
+ local glibc ;
++ return ;
+ if [ feature.values <toolset> ] = gcc
+ {
+ debug-message Checking glibc (ldd) version... ;
Boost is querying the host's ldd for a glibc version instead of the target which leads to reproducibility issues. We shouldn't do this when cross compiling. Patch out the issue for now. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> --- .../boost/boost-build-native_1.92.0.bb | 3 ++- .../boost/boost-build/python-glibc.patch | 19 +++++++++++++++++++ 2 files changed, 21 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-support/boost/boost-build/python-glibc.patch