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

[catalyst@poseidon.amd64.dev.gentoo.org]

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

Using command line specified Catalyst configuration file, /etc/catalyst/amd64-auto.conf
Setting sharedir to config file value "/usr/lib/catalyst/"
Setting snapshot_cache to default value "/var/tmp/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/release/buildroot/amd64-dev"
Setting portdir to config file value "/release/trees/portage-auto"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "ccache pkgcache metadata_overlay autoresume snapcache seedcache kerncache"
Autoresuming support enabled.
Compiler cache support enabled.
Kernel cache support enabled.
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Use of metadata_overlay module for portage enabled.
Envscript support enabled.
Using target: stage2
Building natively for amd64
Source path set to /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20110331/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 /release/buildroot/amd64-dev/builds/default/stage1-amd64-20110331.tar.bz2

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

Starting rsync from /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20110331/tmp/stage1root/
to /release/buildroot/amd64-dev/tmp/default/stage2-amd64-20110331/ (This may take some time) ...

--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: config_profile_link
Configuring profile link...
--- 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 /release/buildroot/amd64-dev/tmp/default/stage2-amd64-20110331/tmp/
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/default/stage2-amd64-20110331/tmp/
Running stage2-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/default/stage2-amd64-20110331/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps --noreplace dev-util/ccache

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



 * IMPORTANT: 2 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

>>> Verifying ebuild manifests
>>> Emerging (1 of 1) dev-util/ccache-2.4-r9
>>> Failed to emerge dev-util/ccache-2.4-r9, Log file:
>>>  '/var/tmp/portage/dev-util/ccache-2.4-r9/temp/build.log'
 * Package:    dev-util/ccache-2.4-r9
 * Repository: gentoo
 * USE:        amd64 elibc_glibc kernel_linux multilib userland_GNU
 * FEATURES:   sandbox
 * Applying ccache-2.4-profile.patch ...
 [ ok ]
 * Applying ccache-2.4-respectflags.patch ...
 [ ok ]
 * Applying ccache-2.4-utimes.patch ...
 [ ok ]
 * Applying ccache-2.4-xrealloc.patch ...
 [ ok ]
 * Running autoconf ...
 [ ok ]
configure: Configuring ccache
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/dev-util/ccache-2.4-r9/work/ccache-2.4':
configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/dev-util/ccache-2.4-r9/work/ccache-2.4/config.log
 * ERROR: dev-util/ccache-2.4-r9 failed (compile phase):
 *   econf failed
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_compile
 *   environment, line 2773:  Called _eapi0_src_compile
 *     ebuild.sh, line  623:  Called econf
 *     ebuild.sh, line  557:  Called die
 * The specific snippet of code:
 *   			die "econf failed"
 * 
 * If you need support, post the output of 'emerge --info =dev-util/ccache-2.4-r9',
 * the complete build log and the output of 'emerge -pqv =dev-util/ccache-2.4-r9'.
 * The complete build log is located at '/var/tmp/portage/dev-util/ccache-2.4-r9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/ccache-2.4-r9/temp/environment'.
 * S: '/var/tmp/portage/dev-util/ccache-2.4-r9/work/ccache-2.4'

 * Messages for package dev-util/ccache-2.4-r9:
 * ERROR: dev-util/ccache-2.4-r9 failed (compile phase):
 *   econf failed
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_compile
 *   environment, line 2773:  Called _eapi0_src_compile
 *     ebuild.sh, line  623:  Called econf
 *     ebuild.sh, line  557:  Called die
 * The specific snippet of code:
 *   			die "econf failed"
 * 
 * If you need support, post the output of 'emerge --info =dev-util/ccache-2.4-r9',
 * the complete build log and the output of 'emerge -pqv =dev-util/ccache-2.4-r9'.
 * The complete build log is located at '/var/tmp/portage/dev-util/ccache-2.4-r9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/ccache-2.4-r9/temp/environment'.
 * S: '/var/tmp/portage/dev-util/ccache-2.4-r9/work/ccache-2.4'


 * IMPORTANT: 2 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.


!!! catalyst: run script failed.


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

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

Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 209, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1263, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1212, 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 '/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20110331/.catalyst_lock'



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