gentoo ~ $ emerge -uav1 boost These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-util/boost-build-1.74.0::gentoo [1.73.0::gentoo] USE="-examples" 0 KiB [ebuild r U ] dev-libs/boost-1.74.0:0/1.74.0::gentoo [1.73.0:0/1.73.0::gentoo] USE="bzip2 python threads zlib -context -debug -doc -icu -lzma -mpi -nls -numpy -static-libs -tools -zstd" PYTHON_TARGETS="python3_6 python3_7 python3_8 -python2_7 -python3_9%" 0 KiB [ebuild rR ] dev-util/intel-ocl-sdk-4.4.0.117-r2::gentoo USE="system-boost system-tbb -android (-system-clang)" 0 KiB [ebuild rR ] dev-libs/collada-dom-2.5.0:0/25::gentoo 0 KiB Total: 4 packages (2 upgrades, 2 reinstalls), Size of downloads: 0 KiB The following packages are causing rebuilds: (dev-libs/boost-1.74.0:0/1.74.0::gentoo, ebuild scheduled for merge) causes rebuilds for: (dev-util/intel-ocl-sdk-4.4.0.117-r2:0/0::gentoo, ebuild scheduled for merge) (dev-libs/collada-dom-2.5.0:0/25::gentoo, ebuild scheduled for merge) Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Emerging (1 of 4) dev-util/boost-build-1.74.0::gentoo * Fetching files in the background. * To view fetch progress, run in another terminal: * tail -f /cvmfs/sft.cern.ch/lcg/contrib/gentoo/linux/x86_64/var/log/emerge-fetch.log * boost_1_74_0.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Source unpacked in /tmp/portage/dev-util/boost-build-1.74.0/work >>> Preparing source in /tmp/portage/dev-util/boost-build-1.74.0/work/boost_1_74_0/tools/build/src ... * Applying boost-build-1.71.0-disable_python_rpath.patch ... [ ok ] * Applying boost-build-1.71.0-darwin-gentoo-toolchain.patch ... [ ok ] * Applying boost-build-1.73.0-add-none-feature-options.patch ... [ ok ] * Applying boost-build-1.71.0-respect-c_ld-flags.patch ... [ ok ] * Applying boost-build-1.74.0-no-implicit-march-flags.patch ... [ ok ] * Applying boost-build-1.71.0-fix-test.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /tmp/portage/dev-util/boost-build-1.74.0/work/boost_1_74_0/tools/build/src ... * Adjusting to prefix /cvmfs/sft.cern.ch/lcg/contrib/gentoo/linux/x86_64 * ERROR: dev-util/boost-build-1.74.0::gentoo failed (configure phase): * engine/Jambase does not exist * * Call stack: * ebuild.sh, line 125: Called src_configure * environment, line 1584: Called hprefixify 'engine/Jambase' * environment, line 1165: Called die * The specific snippet of code: * die "${x} does not exist"; * * If you need support, post the output of `emerge --info '=dev-util/boost-build-1.74.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-util/boost-build-1.74.0::gentoo'`. * The complete build log is located at '/tmp/portage/log/dev-util:boost-build-1.74.0:20200818-063752.log'. * For convenience, a symlink to the build log is located at '/tmp/portage/dev-util/boost-build-1.74.0/temp/build.log'. * The ebuild environment file is located at '/tmp/portage/dev-util/boost-build-1.74.0/temp/environment'. * Working directory: '/tmp/portage/dev-util/boost-build-1.74.0/work/boost_1_74_0/tools/build/src' * S: '/tmp/portage/dev-util/boost-build-1.74.0/work/boost_1_74_0/tools/build/src'
Created attachment 664396 [details, diff] hprefixify Patch I grepped through the sources and came up with this list of files to patch. Although there are not many boost-dependencies in my tree, it seems to work here. Comments welcome.
(In reply to Christian Ludwig from comment #1) > Created attachment 664396 [details, diff] [details, diff] > hprefixify Patch > > I grepped through the sources and came up with this list of files to patch. > > Although there are not many boost-dependencies in my tree, it seems to work > here. > > Comments welcome. I think engine/execunix.cpp and engine/build.sh are ok, but what triggered for you in build-system.jam that needs hprefixify?
boost-build-1.75.0 builds fine for me
