dev-util/boost-build: run hprefixify on engine/Jambase
authorMichael Haubenwallner <haubi@gentoo.org>
Tue, 18 Jun 2019 12:11:23 +0000 (14:11 +0200)
committerMichael Haubenwallner <haubi@gentoo.org>
Wed, 19 Jun 2019 07:32:15 +0000 (09:32 +0200)
commit04985d5d9f35c0810aa070db1c0244bd027c6f28
tree65238a382714bcf41ac7a086987130776ed0a841
parent3321933c10a4bd36e24755d69da54b16dd6bb665
dev-util/boost-build: run hprefixify on engine/Jambase

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>
dev-util/boost-build/boost-build-1.65.0.ebuild
dev-util/boost-build/boost-build-1.70.0.ebuild