* Applying sed/1.5.6 patch ... * Applying as-needed/2.4.3 patch ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/app-crypt/loop-aes-losetup-2.35.2/work/util-linux-2.35.2 ... * ERROR: app-crypt/loop-aes-losetup-2.35.2::gentoo failed (configure phase): * (no error message) * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-j4-20220915-203738 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-12.2.0 * 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: (none found) Available Rust versions: [1] rust-bin-1.63.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.16.1_p1 [openjdk-bin-11] *) Eclipse Temurin JDK 17.0.4.1_p1 [openjdk-bin-17] 3) Eclipse Temurin JDK 8.345_p01 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 [3] openjdk-bin-17 system-vm The Glorious Glasgow Haskell Compilation System, version 9.0.2 php cli (if any): [1] php8.1 * GNU Make 4.3.90 HEAD of ::gentoo commit 2be4f11d1103e9d0fe6cdcf770492a7d6c7ab1e5 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Sep 17 11:01:50 2022 +0000 2022-09-17 11:01:49 UTC emerge -qpvO app-crypt/loop-aes-losetup [ebuild N ] app-crypt/loop-aes-losetup-2.35.2 USE="nls (-selinux) -static"
Created attachment 807526 [details] emerge-info.txt
Created attachment 807529 [details] app-crypt:loop-aes-losetup-2.35.2:20220917-122915.log
Created attachment 807532 [details] emerge-history.txt
Created attachment 807535 [details] environment
Created attachment 807538 [details] etc.portage.tar.bz2
Created attachment 807541 [details] temp.tar.bz2
Confirmed, can't build loop-aes-losetup with CC=clang However, loop-aes-losetup basically just builds a modified losetup from util-linux. And I get the same failure trying to build current util-linux with CC=clang. loop-aes-losetup can't be fixed until util-linux has been fixed.
I wonder why we don't have a bug open for util-linux to track this further.
(In reply to Joonas Niilola from comment #8) > I wonder why we don't have a bug open for util-linux to track this further. I wonder too ;) I could not find one for util-linux, but figured there's no way some tinderbox run tested out loop-aes-losetup before testing util-linux, so maybe my bugzilla foo is lacking, or, the tinderbox tests were against some local branch of ::gentoo that's not merged yet, that already contains util-linux fixes. At the same time, I'm not sure my local reproduction of "CC=clang breaks util-linux" is done "correctly", so would rather not create such a bug myself in case it's just noise.
