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

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

Catalyst, version 2.0.17
Copyright 2003-2008 Gentoo Foundation
Copyright 2008-2012 various authors
Distributed under the GNU General Public License version 2.1

Using command line specified Catalyst configuration file, /etc/catalyst/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to config file value "/usr/local/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/usr/local/catalyst"
Setting portdir to config file value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "autoresume bindist pkgcache seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: stage1
Building natively for hppa
stage1 root path is /tmp/stage1root
Source path set to /usr/local/catalyst/builds/default/stage3-hppa2.0-latest.tar.bz2
Caching snapshot to /usr/local/catalyst/snapshot_cache/20141017/
The autoresume path is /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20141017/
stage1 stage path is /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/tmp/stage1root
Location of the package cache is /usr/local/catalyst/packages/default/stage1-hppa2.0-20141017/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20141017/
>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 
clearing autoresume ...
Removing AutoResume Points: ...
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20141017/
clearing chroot ...
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/
clearing package cache ...
purging the pkgcache ...
clearing kerncache ...
--- Running action sequence: unpack
Referenced SEEDCACHE does not appear to be a directory, trying to untar...
No Valid Resume point detected, cleaning up...
Removing AutoResume Points: ...
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20141017/
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/

Starting tar extract from /usr/local/catalyst/builds/default/stage3-hppa2.0-latest.tar.bz2
to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/ (This may take some time) ...

--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: setup_confdir
--- Running action sequence: portage_overlay
--- Running action sequence: base_dirs
--- Running action sequence: bind
--- Running action sequence: chroot_setup
Setting up chroot...

Warning!!!!
	Overriding certain env variables may cause catastrophic failure.
	If your build fails look here first as the possible problem.
	Catalyst assumes you know what you are doing when setting
		these variables.
	Catalyst Maintainers use VERY minimal envscripts if used at all
	You have been warned

--- Running action sequence: setup_environment
--- Running action sequence: run_local
copying make.conf to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017///tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017//tmp
copying chroot-functions.sh to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017//tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot /usr/local/catalyst/tmp/default/stage1-hppa2.0-20141017/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --oneshot --nodeps --update sys-apps/portage

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)


>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.2.8-r2
>>> Installing (1 of 1) sys-apps/portage-2.2.8-r2
Updating seed stage...
emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc

!!! The following installed packages are masked:
- virtual/perl-ExtUtils-Install-1.580.0-r1::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Andreas K. Huettel <dilfridge@gentoo.org> (9 Oct 2014)
# Masked for removal in 30 days; see e.g. bug 446376
# Please upgrade to stable Perl 5.18

- virtual/perl-File-Temp-0.220.0-r3::gentoo (masked by: package.mask)
- dev-lang/perl-5.16.3::gentoo (masked by: package.mask)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

>>> Recording sys-devel/gcc:4.7 in "world" favorites file...
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-devel/gcc-4.8.3
>>> Emerging (1 of 3) sys-libs/timezone-data-2014g
>>> Installing (1 of 3) sys-libs/timezone-data-2014g
>>> Emerging (2 of 3) sys-libs/glibc-2.19-r1
>>> Installing (2 of 3) sys-libs/glibc-2.19-r1
>>> Emerging (3 of 3) sys-devel/gcc-4.8.3
>>> Failed to emerge sys-devel/gcc-4.8.3

 * Messages for package sys-libs/timezone-data-2014g:

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

 * 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
 * The ebuild phase 'other' 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-devel/gcc-4.8.3:


!!! 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-hppa2.0-20141017/.catalyst_lock'



Full build log at /tmp/catalyst-auto.23296/log/hppa2.0_stage1.log