build log

build.log (text/plain), 3.12 KB, created by Michael Palimaka (kensington) on 2013-11-21 17:21:35 UTC

[32;01m * [39;49;00mPackage:    dev-perl/Term-ReadLine-Perl-1.30.300-r1
[32;01m * [39;49;00mRepository: gentoo
[32;01m * [39;49;00mMaintainer: [e-mail]
[32;01m * [39;49;00mUSE:        amd64 elibc_glibc kernel_linux userland_GNU
[32;01m * [39;49;00mFEATURES:   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 ...
 [32;01m*[0m Using ExtUtils::MakeMaker
 [32;01m*[0m 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 ...
 [32;01m*[0m 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.
 [32;01m*[0m 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.

[31;01m * [39;49;00mThe ebuild phase 'test' has exited unexpectedly. This type of behavior
[31;01m * [39;49;00mis known to be triggered by things such as failed variable assignments
[31;01m * [39;49;00m(bug #190128) or bad substitution errors (bug #200313). Normally, before
[31;01m * [39;49;00mexiting, bash should have displayed an error message above. If bash did
[31;01m * [39;49;00mnot produce an error message above, it's possible that the ebuild has
[31;01m * [39;49;00mcalled `exit` when it should have called `die` instead. This behavior
[31;01m * [39;49;00mmay also be triggered by a corrupt bash binary or a hardware problem
[31;01m * [39;49;00msuch as memory or cpu malfunction. If the problem is not reproducible or
[31;01m * [39;49;00mit appears to occur randomly, then it is likely to be triggered by a
[31;01m * [39;49;00mhardware problem. If you suspect a hardware problem then you should try
[31;01m * [39;49;00msome basic hardware diagnostics such as memtest. Please do not report
[31;01m * [39;49;00mthis as a bug unless it is consistently reproducible and you are sure
[31;01m * [39;49;00mthat your bash binary and hardware are functioning properly.