engine/Jambase defines default locations for boost-build, which should
stick to the EPREFIX where installed to, not the host system.
The breakage is in prefix-stack, where the boost ebuild does add the
stacked EPREFIX only as --boost-build flag, but not BROOT. Although
this is questionable, we really should use our own prefix as fallback.
Package-Manager: Portage-2.3.66, Repoman-2.3.11
Signed-off-by: Michael Haubenwallner <haubi@gentoo.org>
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
RESTRICT="test"
PYTHON_COMPAT=( python2_7 )
-inherit eutils flag-o-matic python-single-r1 toolchain-funcs versionator
+inherit eutils flag-o-matic prefix python-single-r1 toolchain-funcs versionator
MY_PV="$(replace_all_version_separators _)"
}
src_configure() {
+ hprefixify engine/Jambase
if use python; then
# replace versions by user-selected one (TODO: fix this when slot-op
# deps are available to always match the best version available)
EAPI=7
PYTHON_COMPAT=( python2_7 )
-inherit flag-o-matic python-single-r1 toolchain-funcs
+inherit flag-o-matic prefix python-single-r1 toolchain-funcs
MY_PV="$(ver_rs 1- _)"
}
src_configure() {
+ hprefixify engine/Jambase
if use python; then
# replace versions by user-selected one (TODO: fix this when slot-op
# deps are available to always match the best version available)