checking libblockdev-loop presence... yes checking libblockdev-swap presence... yes checking libblockdev-mdraid presence... yes checking libblockdev-fs presence... yes checking libblockdev-crypto presence... yes checking libblockdev-nvme presence... no configure: error: BLOCKDEV NVMe support requested but header or library not found !!! Please attach the following file when seeking support: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome-20230717-063004 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 16.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/16/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/16 16.0.6 Python 3.11.4 Available Ruby profiles: [1] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.70.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.7_p7 [openjdk-bin-17] 2) Eclipse Temurin JDK 8.372_p07 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 system-vm php cli (if any): go version go1.20.6 linux/amd64 HEAD of ::gentoo commit 2a2510ba7fd2362ef72e2ba1e8d90245ec11b470 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Jul 18 07:47:16 2023 +0000 2023-07-18 07:47:16 UTC emerge -qpvO sys-fs/udisks [ebuild N ] sys-fs/udisks-2.10.0 USE="acl daemon elogind introspection nls -debug -lvm (-selinux) -systemd"
Created attachment 865717 [details] emerge-info.txt
Created attachment 865718 [details] emerge-history.txt
Created attachment 865719 [details] environment
Created attachment 865720 [details] etc.clang.tar.xz
Created attachment 865721 [details] etc.portage.tar.xz
Created attachment 865722 [details] logs.tar.xz
Created attachment 865723 [details] sys-fs:udisks-2.10.0:20230718-094805.log
Created attachment 865724 [details] temp.tar.xz
This is a duplicate of bug 910484
*** This bug has been marked as a duplicate of bug 910484 ***