[gentoo-releng-autobuilds] [hppa-auto] Catalyst fatal build error - hppa1.1/stage1.spec

[catalyst@hake.hppa.dev.gentoo.org]

[0xfaef8004]
[0xfb4f4e0c]
/proc/29431/cmdline: ../../miniperl -I../../lib Makefile.PL INSTALLDIRS=perl INSTALLMAN1DIR=none INSTALLMAN3DIR=none PERL_CORE=1 LIBPERL_A=libperl.so.5.20.2 LINKTYPE=dynamic 

6 from cpan/Time-HiRes's Makefile.PL at make_ext.pl line 508.
 (null)*(null) ../../sandbox-2.6/libsandbox/libsandbox.c:check_syscall():879: failure (No such file or directory):
 (null)*(null) ISE:
	abs_path: (null)
	res_path: (null)
[0xfaef8004]
[0xfb10be0c]
/proc/29430/cmdline: ./miniperl -Ilib make_ext.pl lib/auto/Time/HiRes/HiRes.so MAKE=make LIBPERL_A=libperl.so.5.20.2 LINKTYPE=dynamic 

makefile:592: recipe for target 'lib/auto/Time/HiRes/HiRes.so' failed
make: *** [lib/auto/Time/HiRes/HiRes.so] Aborted
 * ERROR: dev-lang/perl-5.20.2::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=dev-lang/perl-5.20.2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-lang/perl-5.20.2::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-lang/perl-5.20.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lang/perl-5.20.2/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-lang/perl-5.20.2/work/perl-5.20.2'
 * S: '/var/tmp/portage/dev-lang/perl-5.20.2/work/perl-5.20.2'
ebuild-ipc: daemon process not detected
 * The ebuild phase 'compile' 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.
ebuild-ipc: daemon process not detected
 * The ebuild phase 'die_hooks' 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.

 * Messages for package sys-libs/timezone-data-2015b:

 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.

 * Messages for package sys-apps/sysvinit-2.88-r7:

 * The last/lastb/mesg/mountpoint/sulogin/utmpdump/wall tools have been moved to
 * sys-apps/util-linux. The pidof tool has been moved to sys-process/procps.

 * Messages for package sys-apps/coreutils-8.23:

 * Make sure you run 'hash -r' in your active shells.
 * You should also re-source your shell settings for LS_COLORS
 *   changes, such as: source /etc/profile

 * Messages for package sys-libs/pam-1.2.1:

 * Some software with pre-loaded PAM libraries might experience
 * warnings or failures related to missing symbols and/or versions
 * after any update. While unfortunate this is a limit of the
 * implementation of PAM and the software, and it requires you to
 * restart the software manually after the update.
 * 
 * You can get a list of such software running a command like
 *   lsof / | egrep -i 'del.*libpam\.so'
 * 
 * Alternatively, simply reboot your system.

 * Messages for package sys-apps/busybox-1.23.1-r1:

 * Could not locate user configfile, so we will save a default one
 * You cannot have USE='static pam'.  Assuming static is more important.
 * Your configuration for sys-apps/busybox-1.23.1-r1 has been saved in 
 * /etc/portage/savedconfig/sys-apps/busybox-1.23.1-r1 for your editing pleasure.
 * You can edit these files by hand and remerge this package with
 * USE=savedconfig to customise the configuration.
 * You can rename this file/directory to one of the following for
 * its configuration to apply to multiple versions:
 * ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
 * [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]

 * Messages for package sys-libs/glibc-2.19-r1:

 * Defaulting /etc/host.conf:multi to on
 * Generating all locales; edit /etc/locale.gen to save time/space

 * Messages for package sys-apps/util-linux-2.25.2-r2:

 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.

 * Messages for package sys-apps/openrc-0.17:

 * Auto-adding 'binfmt' service to your boot runlevel
 * Setting the console font does not work on all HPPA consoles.
 * You can still enable it by running:
 * # rc-update add consolefont boot
 * In this version of OpenRC, the loopback interface no longer
 * satisfies the net virtual.
 * If you have services now which do not start because of this,
 * They can be fixed by adding rc_need="!net"
 * to the /etc/conf.d/<servicename> file.
 * You should also file a bug against the service asking that
 * need net be dropped from the dependencies.
 * The bug you file should block the following tracker:
 * https://bugs.gentoo.org/show_bug.cgi?id=439092
 * 
 * Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not
 * fixed correctly in earlier versions of OpenRC.
 * The correct fix is implemented in this version, but that
 * means netmount needs to be added to the default runlevel if
 * you are using nfs file systems.
 * 
 * You should now update all files in /etc, using etc-update
 * or equivalent before restarting any services or this host.

 * Messages for package sys-devel/gcc-4.8.4:

 * If you have issues with packages unable to locate libstdc++.la,
 * then try running 'fix_libtool_files.sh' on the old gcc versions.
 * You might want to review the GCC upgrade guide when moving between
 * major versions (like 4.2 to 4.3):
 * http://www.gentoo.org/doc/en/gcc-upgrading.xml

 * Messages for package net-misc/openssh-6.9_p1-r2:

 * Remember to merge your config files in /etc/ssh/ and then
 * reload sshd: '/etc/init.d/sshd reload'.
 * Note: openssh-6.7 versions no longer support USE=tcpd as upstream has
 *       dropped it.  Make sure to update any configs that you might have.

 * Messages for package dev-lang/perl-5.20.2:

 * UPDATE THE PERL MODULES:
 * After updating dev-lang/perl you must reinstall
 * the installed perl modules.
 * Use: perl-cleaner --all
 * The ebuild phase 'compile' 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.
 * ERROR: dev-lang/perl-5.20.2::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=dev-lang/perl-5.20.2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-lang/perl-5.20.2::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-lang/perl-5.20.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lang/perl-5.20.2/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-lang/perl-5.20.2/work/perl-5.20.2'
 * S: '/var/tmp/portage/dev-lang/perl-5.20.2/work/perl-5.20.2'

!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1244, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: Stage build aborting due to error.

Traceback (most recent call last):
File "/usr/lib/catalyst/catalyst", line 218, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1304, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1249, in run_local
    raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage1
Catalyst aborting....
lockfile does not exist '/usr/local/catalyst/tmp/default/stage1-hppa1.1-20150731/.catalyst_lock'



Full build log at /tmp/catalyst-auto.PsEE2a/log/hppa1.1_stage1.log