from /usr/lib/gcc/x86_64-gentoo-linux-musl/12.1.1/include/g++-v12/memory:77, from /var/tmp/portage/dev-util/mingw64-toolchain-10.0.0-r1/work/gcc/gcc/../libcody/cody.hh:24, from /var/tmp/portage/dev-util/mingw64-toolchain-10.0.0-r1/work/gcc/gcc/cp/mapper-client.h:26, from /var/tmp/portage/dev-util/mingw64-toolchain-10.0.0-r1/work/gcc/gcc/cp/mapper-client.cc:34: /usr/include/sched.h:84:7: error: attempt to use poisoned "calloc" 84 | void *calloc(size_t, size_t); | ^ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-j4-20220628-041652 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-12.1.1 * clang/llvm (if any): clang version 14.0.6 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/14/bin /usr/lib/llvm/14 14.0.6 Python 3.9.13 Available Rust versions: [1] rust-1.61.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.3_p7 [openjdk-bin-17] Available Java Virtual Machines: [1] openjdk-bin-17 system-vm php cli: HEAD of ::gentoo commit 00c986b747fd05fc0d90acd6699bf76f43e0b6c6 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Jun 28 21:16:28 2022 +0000 2022-06-28 21:16:28 UTC emerge -qpvO dev-util/mingw64-toolchain [ebuild N ] dev-util/mingw64-toolchain-10.0.0-r1 USE="-custom-cflags -debug"
Created attachment 788576 [details] emerge-info.txt
Created attachment 788579 [details] dev-util:mingw64-toolchain-10.0.0-r1:20220628-230343.log.bz2
Created attachment 788582 [details] emerge-history.txt
Created attachment 788585 [details] environment
Created attachment 788588 [details] etc.portage.tar.bz2
Created attachment 788591 [details] logs.tar.bz2
The file size of ./files/temp.tar.bz2 is too big (62M) for an upload. For about 8 weeks the link http://tinderbox.zwiebeltoralf.de:31560/17.0_musl-j4-20220628-041652/var/tmp/tb/issues/20220629-012442-dev-util_mingw64-toolchain-10.0.0-r1/files/temp.tar.bz2 is valid.
Unsure how useful this is on musl but guess could add gentoo musl patches anyway, reassigning to myself.
(In reply to Ionen Wolkens from comment #8) > Unsure how useful this is on musl but guess could add gentoo musl patches > anyway, reassigning to myself. Uh wait there's more to this, is fine regardless of the patchset with gcc:11 but fails only if building with gcc:12? And mingw64-toolchain has gcc-11.3.0 while the musl :11 patchset doesn't have the calloc fixes, guess I'll just take the non-jit bits from gcc:12 patchset (don't think other musl patches matter given this isn't a musl target).
There's https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106102 too.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d8f263e503f54eb05f2c764ae443ea2e08e47366 commit d8f263e503f54eb05f2c764ae443ea2e08e47366 Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2022-06-29 16:23:21 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2022-06-29 17:22:36 +0000 dev-util/mingw64-toolchain: fix build with musl and gcc:12 Closes: https://bugs.gentoo.org/855002 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> .../files/gcc-11.3.0-musl-calloc.patch | 33 ++++++++++++++++++++++ .../mingw64-toolchain-10.0.0-r1.ebuild | 1 + 2 files changed, 34 insertions(+)
