at builder/MyBuilder.pm line 4. BEGIN failed--compilation aborted at builder/MyBuilder.pm line 4. Compilation failed in require at Build.PL line 12. BEGIN failed--compilation aborted at Build.PL line 12. * ERROR: dev-perl/Server-Starter-0.330.0::gentoo failed (configure phase): * Unable to build! ----------------------------------------------------------------- This is an unstable amd64 chroot image (named plasma-systemd-libressl-unstable_20170111-153814) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config --version: 3.9.1 Available Python interpreters: [1] python2.7 [2] python3.4 * java-config: -----------------------------------------------------------------
Created attachment 459792 [details] emerge-info.txt
Created attachment 459794 [details] dev-perl:Server-Starter-0.330.0:20170112-163056.log
Created attachment 459796 [details] emerge-history.txt
Created attachment 459798 [details] environment
Created attachment 459800 [details] etc.portage.tbz2
This looks like another case of "Portage doesn't order bdeps properly". Given that this error happens because Module/Build.pm is in none of @INC And Module/Build.pm is not in @INC because: Wed Jan 11 15:58:56 2017 <<< dev-lang/perl-5.22.3_rc4 Wed Jan 11 15:58:58 2017 >>> dev-lang/perl-5.24.1_rc4 And there's no dev-perl/Module-Build between that and the time Server-Starter needed installation. This means this is a variation of bug #596664 and bug #592880, as it is declared as BDEP, but portage hasn't ordered things to ensure its working at build time.
*** This bug has been marked as a duplicate of bug 689644 ***