System: Darwin_Mac-1708751288248.local_22.6.0_Darwin_Kernel_Version_22.6.0__Sun_Dec_17_22_18_09_PST_2023;_root_xnu-8796.141.3.703.2~2_RELEASE_X86_64_x86_64 STABLE prefix Darwin Mac-1708751288248.local 22.6.0 Darwin Kernel Version 22.6.0: Sun Dec 17 22:18:09 PST 2023; root:xnu-8796.141.3.703.2~2/RELEASE_X86_64 x86_64 Steps to reproduce the bug: Run the bootstrap-prefix.sh in mode STABLE (default STABLE) for stage2 (lower ones before) Error message: failed! :( Details might be found in the build log: /Users/runner/work/gentoo-prefix-tester/gentoo-prefix-tester/gentoo-prefix/tmp/var/tmp/portage/sys-devel/gcc-13.2.0/temp/build.log (no build logs found?!?) I have no clue, really. Please find friendly folks in #gentoo-prefix on irc.gentoo.org, gentoo-alt@lists.gentoo.org mailing list, or file a bug at bugs.gentoo.org under Gentoo/Alt, Prefix Support. Remember you might find some clues in /Users/runner/work/gentoo-prefix-tester/gentoo-prefix-tester/gentoo-prefix/stage2.log CHOST: x86_64-apple-darwin22 IDENT: x86_64-apple-darwin22 Extra info: https://github.com/APN-Pucky/gentoo-prefix-tester/actions/runs/8028690890
Created attachment 885826 [details] full_stage2_STABLE_Darwin_Mac-1708751288248.local_22.6.0_Darwin_Kernel_Version_22.6.0__Sun_Dec_17_22_18_09_PST_2023;_root_xnu-8796.141.3.703.2~2_RELEASE_X86_64_x86_64_20240224063444.log.xz
Created attachment 885827 [details] build_stage2_STABLE_Darwin_Mac-1708751288248.local_22.6.0_Darwin_Kernel_Version_22.6.0__Sun_Dec_17_22_18_09_PST_2023;_root_xnu-8796.141.3.703.2~2_RELEASE_X86_64_x86_64_20240224063444.log.xz
You are not using the latest bootstrap-prefix.sh script, and therefore most likely are not using a correct SDK. Please make sure your automated bootstraps always fetch the latest bootstrap-prefix.sh from the (rsync) mirrors.
I am looking into this. wget reported this (outdated by now): 2024-02-24 06:06:52 (75.3 MB/s) - ‘bootstrap-prefix.sh’ saved [106982/106982] Wget locally gives me the same size as on github. I'll update it to add a md5sum of the bootstrap file to the bugzilla message to be sure.
*** Bug 925490 has been marked as a duplicate of this bug. ***