* Package: dev-perl/Term-ReadLine-Perl-1.30.300-r1  * Repository: gentoo  * Maintainer: perl@gentoo.org  * USE: amd64 elibc_glibc kernel_linux userland_GNU  * FEATURES: preserve-libs sandbox splitdebug test userpriv usersandbox >>> Unpacking source... >>> Unpacking Term-ReadLine-Perl-1.0303.tar.gz to /var/tmp/portage/dev-perl/Term-ReadLine-Perl-1.30.300-r1/work >>> Source unpacked in /var/tmp/portage/dev-perl/Term-ReadLine-Perl-1.30.300-r1/work >>> Preparing source in /var/tmp/portage/dev-perl/Term-ReadLine-Perl-1.30.300-r1/work/Term-ReadLine-Perl-1.0303 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-perl/Term-ReadLine-Perl-1.30.300-r1/work/Term-ReadLine-Perl-1.0303 ... * Using ExtUtils::MakeMaker * perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none DESTDIR=/var/tmp/portage/dev-perl/Term-ReadLine-Perl-1.30.300-r1/image/ Checking if your kit is complete... Looks good Writing Makefile for Term::ReadLine Writing MYMETA.yml and MYMETA.json >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-perl/Term-ReadLine-Perl-1.30.300-r1/work/Term-ReadLine-Perl-1.0303 ... * emake OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu make -j4 'OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu' cp ReadLine/Perl.pm blib/lib/Term/ReadLine/Perl.pm cp ReadLine/readline.pm blib/lib/Term/ReadLine/readline.pm >>> Source compiled. * Test::Harness Jobs=4 make -j4 test TEST_VERBOSE=0 PERL_DL_NONLAZY=1 /usr/bin/perl5.16.3 "-Iblib/lib" "-Iblib/arch" test.pl Use of uninitialized value $ENV{"PERL_RL_TEST_PROMPT_MINLEN"} in bitwise or (|) at test.pl line 33. at test.pl line 33. sandbox:stop caught signal 2 in pid 2354 make: *** [test_dynamic] Interrupt /usr/portage/dev-perl/Term-ReadLine-Perl/Term-ReadLine-Perl-1.30.300-r1.ebuild: __dyn_test aborted; exiting.  * The ebuild phase 'test' has exited unexpectedly. This type of behavior  * is known to be triggered by things such as failed variable assignments  * (bug #190128) or bad substitution errors (bug #200313). Normally, before  * exiting, bash should have displayed an error message above. If bash did  * not produce an error message above, it's possible that the ebuild has  * called `exit` when it should have called `die` instead. This behavior  * may also be triggered by a corrupt bash binary or a hardware problem  * such as memory or cpu malfunction. If the problem is not reproducible or  * it appears to occur randomly, then it is likely to be triggered by a  * hardware problem. If you suspect a hardware problem then you should try  * some basic hardware diagnostics such as memtest. Please do not report  * this as a bug unless it is consistently reproducible and you are sure  * that your bash binary and hardware are functioning properly.