* Repository: gentoo * Maintainer: blueness@gentoo.org lu_zero@gentoo.org,toolchain@gentoo.org,musl@gentoo.org * USE: abi_x86_64 amd64 crypt elibc_glibc kernel_linux userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * ERROR: sys-libs/musl-1.2.3-r1::gentoo failed (setup phase): * Use sys-devel/crossdev to build a musl toolchain ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no_multilib_systemd-j4-20220908-070011 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-12.2.1 * clang/llvm (if any): clang version 15.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/15/bin /usr/lib/llvm/15 15.0.0 Python 3.10.7 Available Ruby profiles: [1] ruby27 (with Rubygems) [2] ruby31 (with Rubygems) * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.15_p10 [openjdk-bin-11] 2) Eclipse Temurin JDK 17.0.3_p7 [openjdk-bin-17] *) Eclipse Temurin JDK 8.332_p09 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm [2] openjdk-bin-11 [3] openjdk-bin-17 The Glorious Glasgow Haskell Compilation System, version 9.0.2 php cli (if any): [1] php7.4 * [2] php8.0 [3] php8.1 GNU Make 4.3 HEAD of ::gentoo commit ecaf130923b089d04d17ac9149b7abad826079ce Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Sep 10 12:27:46 2022 +0000 2022-09-10 12:27:46 UTC emerge -qpvO sys-libs/musl [ebuild N ] sys-libs/musl-1.2.3-r1 USE="crypt -headers-only -verify-sig"
Created attachment 804469 [details] emerge-info.txt
Created attachment 804472 [details] die.env
Created attachment 804475 [details] emerge-history.txt.bz2
Created attachment 804478 [details] etc.portage.tar.bz2
Created attachment 804481 [details] logs.tar.bz2
Created attachment 804484 [details] sys-libs:musl-1.2.3-r1:20220910-132125.log
I'm not sure whether I should ignore such issues -or- if the ebuild should block those deps ?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e617820e9eba576c0546c2a756a1b564370aa43b commit e617820e9eba576c0546c2a756a1b564370aa43b Author: Sam James <sam@gentoo.org> AuthorDate: 2022-09-10 13:31:48 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-09-10 13:48:31 +0000 profiles: mask/unmask musl on musl/non musl profiles Closes: https://bugs.gentoo.org/869515 Signed-off-by: Sam James <sam@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/27199 Signed-off-by: Sam James <sam@gentoo.org> profiles/base/package.mask | 6 +++++- profiles/features/musl/package.mask | 1 + 2 files changed, 6 insertions(+), 1 deletion(-)
(In reply to Toralf Förster from comment #7) > I'm not sure whether I should ignore such issues -or- if the ebuild should > block those deps ? I think do report them and we can discuss if something is a special case or not. Nice find, thanks!
