* ERROR: dev-perl/Coro-6.514.0::gentoo failed (configure phase): * Unable to build! * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200328-141627 ------------------------------------------------------------------- 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.42.0 * timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Wed Apr 1 19:37:27 UTC 2020 /var/db/repos/musl Fri Mar 27 00:25:27 UTC 2020 emerge -qpvO dev-perl/Coro [ebuild N ] dev-perl/Coro-6.514.0 USE="ev -event -examples"
Created attachment 628584 [details] emerge-info.txt
Created attachment 628586 [details] dev-perl:Coro-6.514.0:20200401-201020.log
Created attachment 628588 [details] emerge-history.txt
Created attachment 628590 [details] environment
Created attachment 628592 [details] etc.portage.tbz2
Created attachment 628594 [details] temp.tbz2
/var/tmp/portage/dev-perl/Coro-6.514.0/temp/environment: line 468: 16804 Segmentation fault perl Makefile.PL "$@" <<< "${pm_echovar}" * ERROR: dev-perl/Coro-6.514.0::gentoo failed (configure phase): * Unable to build! * * Call stack: * ebuild.sh, line 125: Called src_configure * environment, line 932: Called perl-module_src_configure * environment, line 505: Called die * The specific snippet of code: * perl Makefile.PL "$@" <<< "${pm_echovar}" || die "Unable to build!"; Er, yeah, this indicates your perl install here is *probably* screwed. There's no way to work out what is happening here other than stepping through the execution of Makefile.PL and working out where it trips into a segfault. This will have to be musl teams responsibility to diagnose, and if they can find the problem, then I might be able to fix it. ( Try the latest coro though, it might have fixes, ... though I doubt it very much. )
Works fine on musl with recent Perl and recent Coro.