Michael Haubenwallner 04985d5d9f 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>

2019-06-19 09:32:15 +02:00

..

files

…

boost-build-1.65.0.ebuild

dev-util/boost-build: run hprefixify on engine/Jambase

2019-06-19 09:32:15 +02:00

boost-build-1.70.0.ebuild

dev-util/boost-build: run hprefixify on engine/Jambase

2019-06-19 09:32:15 +02:00

Manifest

dev-util/boost-build: Remove old

2019-04-21 21:18:08 +02:00

metadata.xml

…