In file included from logging.c:32: logging.c: In function rxvt_makeutent: rxvt.h:457:29: error: LASTLOG_FILENAME undeclared (first use in this function); did you mean WTMP_FILENAME? 457 | # define RXVT_LASTLOG_FILE LASTLOG_FILENAME | ^~~~~~~~~~~~~~~~ logging.c:236:22: note: in expansion of macro RXVT_LASTLOG_FILE ------------------------------------------------------------------- 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-bin-1.41.1 [2] rust-1.41.1 * The following VMs are available for generation-2: repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Mon, 16 Mar 2020 10:40:49 +0000 emerge -qpvO x11-terms/mrxvt [ebuild N ] x11-terms/mrxvt-0.5.4 USE="-debug -jpeg -menubar -png -session -truetype -utempter -xpm" L10N="-el -ja -ko -th -zh-CN -zh-TW"
Created attachment 620592 [details] emerge-info.txt
Created attachment 620594 [details] emerge-history.txt
Created attachment 620596 [details] environment
Created attachment 620598 [details] etc.portage.tbz2
Created attachment 620600 [details] logs.tbz2
Created attachment 620602 [details] temp.tbz2
Created attachment 620604 [details] x11-terms:mrxvt-0.5.4:20200316-113418.log
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.
