| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Package-Manager: Portage-2.3.81, Repoman-2.3.19
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/689278
Package-Manager: Portage-2.3.71, Repoman-2.3.17
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
* bzip2/lzma/zlib/zstd support can now be
disabled via USE flags explicitly.
* Upstream has fixed Boost.Python to finally
support building against multiple Python 3
implementations concurrently:
https://github.com/boostorg/python/commit/d4d41d94aecc
Going forward, Gentoo will stop modifying
the upstream build system for its multiple
implementations. This will lead to some
short-term pain, as the library pattern changes
from
libboost_python-3.6.so
to
libboost_python36.so
which is the canonical name used by upstream.
Changing this name should be avoided, as the
filename is also encoded as a macro in various
boost headers.
Bug: https://bugs.gentoo.org/631590
Closes: https://bugs.gentoo.org/653878
Closes: https://github.com/gentoo/gentoo/pull/11659
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: David Seifert <soap@gentoo.org>
|