/usr/bin/cmake -E cmake_link_script CMakeFiles/CrazyDiskInfo.dir/link.txt --verbose=1 /usr/bin/x86_64-gentoo-linux-musl-g++ -Wall -std=c++11 -Wl,-O1 -Wl,--as-needed -rdynamic CMakeFiles/CrazyDiskInfo.dir/main.cpp.o -o crazy -latasmart -lncursesw /usr/lib/gcc/x86_64-gentoo-linux-musl/9.3.0/../../../../x86_64-gentoo-linux-musl/bin/ld: CMakeFiles/CrazyDiskInfo.dir/main.cpp.o: undefined reference to symbol stdscr /usr/lib/gcc/x86_64-gentoo-linux-musl/9.3.0/../../../../x86_64-gentoo-linux-musl/bin/ld: /lib/libtinfow.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/CrazyDiskInfo.dir/build.make:84: crazy] Error 1 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200316-165821 ------------------------------------------------------------------- gcc-config -l: [1] 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 * [2] rust-bin-1.42.0 timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Tue Mar 24 10:38:45 UTC 2020 /var/db/repos/musl Sun Mar 22 15:02:57 UTC 2020 emerge -qpvO sys-apps/crazydiskinfo [ebuild N ] sys-apps/crazydiskinfo-1.0.2
Created attachment 625080 [details] emerge-info.txt
Created attachment 625082 [details] emerge-history.txt
Created attachment 625084 [details] environment
Created attachment 625086 [details] etc.portage.tbz2
Created attachment 625088 [details] logs.tbz2
Created attachment 625090 [details] sys-apps:crazydiskinfo-1.0.2:20200324-111010.log
Created attachment 625092 [details] temp.tbz2
sys-apps/crazydiskinfo-1.0.2 is no longer in the tree and I cannot reproduce the issue with version 1.1.0. Closing.