checking Non-standard OpenSSL location... no checking for Tspi_Context_Create in -ltspi... no configure: error: tss lib not found: libtspi.so !!! Please attach the following file when seeking support: !!! /var/tmp/portage/app-crypt/tpm-tools-1.3.9.1-r1/work/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200311-204810 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-9.2.0 * [2] x86_64-gentoo-linux-musl-9.3.0 clang version 10.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.41.1 * repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sat, 14 Mar 2020 12:39:55 +0000 emerge -qpvO app-crypt/tpm-tools [ebuild N ] app-crypt/tpm-tools-1.3.9.1-r1 USE="nls -debug -libressl -pkcs11"
Created attachment 618990 [details] emerge-info.txt
Created attachment 618992 [details] app-crypt:tpm-tools-1.3.9.1-r1:20200314-150421.log
Created attachment 618994 [details] emerge-history.txt
Created attachment 618996 [details] environment
Created attachment 618998 [details] etc.portage.tbz2
Created attachment 619000 [details] logs.tbz2
The first attempt to tinderbox a musl image failed at all. I'll mass close therefore all filed bug reports of the last days related to this tinderbox image. Please feel free to re-open if you think that the bug is real in musl and not fixed by the musl overlay.
