too long lines were shrinked: [4/9] /usr/bin/x86_64-gentoo-linux-musl-g++ -Dptytty_EXPORTS -I/var/tmp/portage/dev-libs/libptytty-2.0/work/libptytty-2.0_build -pipe -march=native -fno-diagnostics-color -O2 -fPIC -std=gnu++11 -MD -MT CMakeFiles/ptytty.dir/src/logging.C.o -MF CMakeFiles/ptytty.dir/src/logging.C.o.d -o CMakeFiles/p FAILED: CMakeFiles/ptytty.dir/src/logging.C.o /usr/bin/x86_64-gentoo-linux-musl-g++ -Dptytty_EXPORTS -I/var/tmp/portage/dev-libs/libptytty-2.0/work/libptytty-2.0_build -pipe -march=native -fno-diagnostics-color -O2 -fPIC -std=gnu++11 -MD -MT CMakeFiles/ptytty.dir/src/logging.C.o -MF CMakeFiles/ptytty.dir/src/logging.C.o.d -o CMakeFiles/ptytty. /var/tmp/portage/dev-libs/libptytty-2.0/work/libptytty-2.0/src/logging.C: In member function 'void ptytty_unix::log_session(bool, const char*)': /var/tmp/portage/dev-libs/libptytty-2.0/work/libptytty-2.0/src/logging.C:148:17: error: 'WTMPX_FILE' was not declared in this scope 148 | updwtmpx (WTMPX_FILE, &utx); | ^~~~~~~~~~ [5/9] /usr/bin/x86_64-gentoo-linux-musl-g++ -Dptytty_EXPORTS -I/var/tmp/portage/dev-libs/libptytty-2.0/work/libptytty-2.0_build -pipe -march=native -fno-diagnostics-color -O2 -fPIC -std=gnu++11 -MD -MT CMakeFiles/ptytty.dir/src/fdpass.C.o -MF CMakeFiles/ptytty.dir/src/fdpass.C.o.d -o CMakeFiles/pty [6/9] /usr/bin/x86_64-gentoo-linux-musl-g++ -Dptytty_EXPORTS -I/var/tmp/portage/dev-libs/libptytty-2.0/work/libptytty-2.0_build -pipe -march=native -fno-diagnostics-color -O2 -fPIC -std=gnu++11 -MD -MT CMakeFiles/ptytty.dir/src/proxy.C.o -MF CMakeFiles/ptytty.dir/src/proxy.C.o.d -o CMakeFiles/ptytt ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl_hardened-j4-20211210-222208 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-11.2.1 * clang version 13.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/13/bin /usr/lib/llvm/13 13.0.0 Python 3.9.9 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.57.0 * php cli: HEAD of ::gentoo commit 5b3c1757053ea423912ad3d3ff637fe9470f13f1 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Dec 11 09:51:41 2021 +0000 2021-12-11 09:51:40 UTC emerge -qpvO dev-libs/libptytty [ebuild N ] dev-libs/libptytty-2.0
Created attachment 758533 [details] emerge-info.txt
Created attachment 758534 [details] dev-libs:libptytty-2.0:20211211-120437.log
Created attachment 758535 [details] emerge-history.txt
Created attachment 758536 [details] environment
Created attachment 758537 [details] etc.portage.tar.bz2
Created attachment 758538 [details] logs.tar.bz2
Created attachment 758539 [details] temp.tar.bz2
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d0c412924396549a56cbbf19d4b27514abcafa84 commit d0c412924396549a56cbbf19d4b27514abcafa84 Author: Marek Szuba <marecki@gentoo.org> AuthorDate: 2021-12-14 12:00:20 +0000 Commit: Marek Szuba <marecki@gentoo.org> CommitDate: 2021-12-14 12:05:53 +0000 dev-libs/libptytty: fix compilation against musl musl does not define _PATH_{LASTLOGX,UTMPX,WTMPX} so use the upstream-provided CMake arguments to define them ourselves, using the same path convention as what musl headers put in _PATH_{LASTLOG,UTMP,WTMP}. Extra quotes are important, as said variables are currently injected verbatim into headers and hilarity ensues if they are not quoted. Closes: https://bugs.gentoo.org/828923 Signed-off-by: Marek Szuba <marecki@gentoo.org> dev-libs/libptytty/libptytty-2.0.ebuild | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
