* ERROR: sys-libs/ldb-2.2.0-r1::gentoo failed (configure phase): * Invalid use of waf-utils.eclass * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-libressl-20200812-045757 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 10.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.1 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python3.6 (fallback) [5] python2.7 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.45.2 * The following VMs are available for generation-2: The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Sat Aug 15 10:35:47 AM UTC 2020 /var/db/repos/libressl Mon Aug 10 09:13:35 AM UTC 2020 emerge -qpvO sys-libs/ldb [ebuild N ] sys-libs/ldb-2.2.0-r1 USE="ldap lmdb -doc -python -test" PYTHON_SINGLE_TARGET="python3_7 -python3_6 -python3_8"
Created attachment 654770 [details] emerge-info.txt
Created attachment 654772 [details] emerge-history.txt
Created attachment 654774 [details] environment
Created attachment 654776 [details] etc.portage.tbz2
Created attachment 654778 [details] sys-libs:ldb-2.2.0-r1:20200815-112232.log
Created attachment 654780 [details] temp.tbz2
I'm also affected with this bug on sys-libs/ ldb-2.0.12-r1 (marked as stable on amd64)
*** Bug 737242 has been marked as a duplicate of this bug. ***
Hey, I run into this issue, and reported just a few minutes after you :)
ldb compile works find if I revert this commit https://gitweb.gentoo.org/repo/gentoo.git/commit?id=42d6e353
Or try this: # USE=python emerge --nodeps sys-libs/ldb
*** Bug 737258 has been marked as a duplicate of this bug. ***
*** Bug 737262 has been marked as a duplicate of this bug. ***
The patch in github PR fixed it for me (sys-libs/ldb-2.0.12-r1)
I also have run into this problem. USE=python fixed it for me. seems the python-use-flag is always required for this package now.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8e31cbf758673271ca84f5c65f004ca2236ada23 commit 8e31cbf758673271ca84f5c65f004ca2236ada23 Author: David Seifert <soap@gentoo.org> AuthorDate: 2020-08-15 20:31:49 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2020-08-15 20:31:49 +0000 sys-libs/ldb: Require python at build-time unconditionally * waf requires setting up a valid python interpreter before calling waf-utils_src_configure. Closes: https://bugs.gentoo.org/733188 Closes: https://bugs.gentoo.org/737238 Closes: https://github.com/gentoo/gentoo/pull/17126 Package-Manager: Portage-3.0.2, Repoman-2.3.23 Signed-off-by: David Seifert <soap@gentoo.org> sys-libs/ldb/ldb-2.0.12-r1.ebuild | 8 +++++--- sys-libs/ldb/ldb-2.1.4-r1.ebuild | 8 +++++--- sys-libs/ldb/ldb-2.2.0-r1.ebuild | 8 +++++--- 3 files changed, 15 insertions(+), 9 deletions(-)
*** Bug 737274 has been marked as a duplicate of this bug. ***
*** Bug 737430 has been marked as a duplicate of this bug. ***
This is not solved yet. ebuild fails if distcc is enabled. FEATURES=-distcc emerge -1 ldb Does produce a workable result. Probably if waf is used distcc should be disabled. See also: https://bugs.gentoo.org/749267 & https://bugs.gentoo.org/749261
