[gentoo-releng-autobuilds] [alpha-auto] Catalyst fatal build error - stage2.spec

[armin76@gentoo.org]

Setting snapshot_cache to config file value "/space/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/space/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 kerncache pkgcache seedcache snapcache"
Autoresuming support enabled.
Kernel cache support enabled.
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: stage2
Building natively for alpha
Source path set to /space/catalyst/tmp/default/stage1-alpha-20130302/tmp/stage1root/
	If this is not desired, remove this directory or turn of seedcache in the options of catalyst.conf
	the source path will then be /space/catalyst/builds/default/stage1-alpha-20130302.tar.bz2

Caching snapshot to /space/catalyst/snapshot_cache/20130302/
The autoresume path is /space/catalyst/tmp/default/.autoresume-stage2-alpha-20130302/
Location of the package cache is /space/catalyst/packages/default/stage2-alpha-20130302/
Location of the kerncache is /space/catalyst/kerncache/default/stage2-alpha-20130302/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /space/catalyst/tmp/default/.autoresume-stage2-alpha-20130302/
>>> 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 /space/catalyst/tmp/default/.autoresume-stage2-alpha-20130302/
clearing chroot ...
Emptying directory /space/catalyst/tmp/default/stage2-alpha-20130302/
clearing package cache ...
purging the pkgcache ...
clearing kerncache ...
purging the kerncache ...
--- Running action sequence: unpack

Starting rsync from /space/catalyst/tmp/default/stage1-alpha-20130302/tmp/stage1root/
to /space/catalyst/tmp/default/stage2-alpha-20130302/ (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 stage2-chroot.sh to ./tmp
copying stage2-chroot.sh to /space/catalyst/tmp/default/stage2-alpha-20130302/./tmp
copying chroot-functions.sh to /space/catalyst/tmp/default/stage2-alpha-20130302/./tmp
Ensure the file has the executable bit set
Running stage2-chroot.sh in chroot /space/catalyst/tmp/default/stage2-alpha-20130302/
>>> Regenerating /etc/ld.so.cache...

Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2012 Gentoo Foundation; Distributed under the GPLv2
-------------------------------------------------------------------------------
  [[ (0/3) Locating packages ]]
 * Using baselayout : >=sys-apps/baselayout-2
 * Using portage    : portage
 * Using os-headers : >=sys-kernel/linux-headers-3.6
 * Using binutils   : sys-devel/binutils
 * Using gcc        : sys-devel/gcc
 * Using gettext    : gettext
 * Using libc       : virtual/libc
 * Using texinfo    : sys-apps/texinfo
 * Using zlib       : zlib
 * Using ncurses    : ncurses
-------------------------------------------------------------------------------
  [[ (1/3) Configuring environment ]]
-------------------------------------------------------------------------------
  [[ (2/3) Updating 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.1.11.50
>>> Installing (1 of 1) sys-apps/portage-2.1.11.50
-------------------------------------------------------------------------------
  [[ (3/3) Emerging packages ]]
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 10) sys-libs/zlib-1.2.7
>>> Failed to emerge sys-libs/zlib-1.2.7, Log file:
>>>  '/var/tmp/portage/sys-libs/zlib-1.2.7/temp/build.log'
 * Package:    sys-libs/zlib-1.2.7
 * Repository: gentoo
 * USE:        alpha bootstrap elibc_glibc kernel_linux userland_GNU
 * FEATURES:   sandbox
./configure --shared --prefix=/usr --libdir=/usr/lib --uname=linux
Using alpha-unknown-linux-gnu-ar
Using alpha-unknown-linux-gnu-ranlib
Using alpha-unknown-linux-gnu-nm
Checking for alpha-unknown-linux-gnu-gcc...
Checking for shared library support...
No shared library support; try without defining CC and CFLAGS
Building static library libz.a version 1.2.7 with cc.
Checking for off64_t... No.
Checking for fseeko... No.
Checking for strerror... No.
Checking for unistd.h... No.
Checking for stdarg.h... No.
Checking whether to use vs[n]printf() or s[n]printf()... using s[n]printf().
Checking for snprintf() in stdio.h... No.
  WARNING: snprintf() not found, falling back to sprintf(). zlib
  can build but will be open to possible buffer-overflow security
  vulnerabilities.
Checking for return value of sprintf()... No.
  WARNING: apparently sprintf() does not return a value. zlib
  can build but will be open to possible string-format security
  vulnerabilities.
Looking for a four-byte integer type... Not found.
cc -mieee -pipe -O2 -mcpu=ev4 -DNO_FSEEKO -DNO_STRERROR -DNO_snprintf -DHAS_sprintf_void -I. -c -o example.o test/example.c
cc -mieee -pipe -O2 -mcpu=ev4 -DNO_FSEEKO -DNO_STRERROR -DNO_snprintf -DHAS_sprintf_void   -c -o adler32.o adler32.c
cc -mieee -pipe -O2 -mcpu=ev4 -DNO_FSEEKO -DNO_STRERROR -DNO_snprintf -DHAS_sprintf_void   -c -o crc32.o crc32.c
cc -mieee -pipe -O2 -mcpu=ev4 -DNO_FSEEKO -DNO_STRERROR -DNO_snprintf -DHAS_sprintf_void   -c -o deflate.o deflate.c
/usr/libexec/gcc/alpha-unknown-linux-gnu/4.5.4/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory
/usr/libexec/gcc/alpha-unknown-linux-gnu/4.5.4/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory
/usr/libexec/gcc/alpha-unknown-linux-gnu/4.5.4/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory
/usr/libexec/gcc/alpha-unknown-linux-gnu/4.5.4/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory
make: *** [example.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [crc32.o] Error 1
make: *** [adler32.o] Error 1
make: *** [deflate.o] Error 1
emake failed
 * ERROR: sys-libs/zlib-1.2.7 failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 1506:  Called die
 * The specific snippet of code:
 *               emake || die
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/zlib-1.2.7'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/zlib-1.2.7'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/zlib-1.2.7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/zlib-1.2.7/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/zlib-1.2.7/work/zlib-1.2.7'
 * S: '/var/tmp/portage/sys-libs/zlib-1.2.7/work/zlib-1.2.7'
 * Messages for package sys-libs/zlib-1.2.7:
 * ERROR: sys-libs/zlib-1.2.7 failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 1506:  Called die
 * The specific snippet of code:
 *               emake || die
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/zlib-1.2.7'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/zlib-1.2.7'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/zlib-1.2.7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/zlib-1.2.7/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/zlib-1.2.7/work/zlib-1.2.7'
 * S: '/var/tmp/portage/sys-libs/zlib-1.2.7/work/zlib-1.2.7'



!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1230, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, 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 214, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1290, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1235, in run_local
    raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage2
Catalyst aborting....
lockfile does not exist '/space/catalyst/tmp/default/stage2-alpha-20130302/.catalyst_lock'



Full build log at /tmp/catalyst-auto.26398/log/stage2.log