Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-releng-autobuilds
Navigation:
Lists: gentoo-releng-autobuilds: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: releng@g.o,gentoo-releng-autobuilds@g.o
From: armin76@g.o
Subject: [alpha-auto] Catalyst fatal build error - stage2.spec
Date: Sat, 29 Oct 2011 07:33:04 +0200


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 metadata_overlay pkgcache seedcache snapcache"
Autoresuming 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 alpha
Source path set to /space/catalyst/tmp/default/stage1-alpha-20111029/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-20111029.tar.bz2

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

Starting rsync from /space/catalyst/tmp/default/stage1-alpha-20111029/tmp/stage1root/
to /space/catalyst/tmp/default/stage2-alpha-20111029/ (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 /space/catalyst/tmp/default/stage2-alpha-20111029/tmp/
copying chroot-functions.sh to /space/catalyst/tmp/default/stage2-alpha-20111029/tmp/
Running stage2-chroot.sh in chroot /space/catalyst/tmp/default/stage2-alpha-20111029/
>>> Regenerating /etc/ld.so.cache...

Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2011 Gentoo Foundation; Distributed under the GPLv2
-------------------------------------------------------------------------------
  [[ (0/3) Locating packages ]]
 * Using baselayout : sys-apps/baselayout
 * Using portage    : portage
 * Using os-headers : >=sys-kernel/linux-headers-2.6.36.1
 * Using binutils   : sys-devel/binutils
 * Using gcc        : sys-devel/gcc
 * Using gettext    : gettext
 * Using libc       : virtual/libc
 * Using texinfo    : sys-apps/texinfo
 * Using zlib       : sys-libs/zlib
 * Using ncurses    : sys-libs/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.10.11
>>> Installing (1 of 1) sys-apps/portage-2.1.10.11
-------------------------------------------------------------------------------
  [[ (3/3) Emerging packages ]]
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 10) app-arch/xz-utils-5.0.3
>>> Failed to emerge app-arch/xz-utils-5.0.3, Log file:
>>>  '/var/tmp/portage/app-arch/xz-utils-5.0.3/temp/build.log'
 * Package:    app-arch/xz-utils-5.0.3
 * Repository: gentoo
 * USE:        alpha bootstrap elibc_glibc kernel_linux nls userland_GNU
 * FEATURES:   sandbox

XZ Utils 5.0.3

System type:
checking build system type... alpha-unknown-linux-gnu
checking host system type... alpha-unknown-linux-gnu

Configure options:
checking if debugging code should be compiled... no
checking which encoders to build... lzma1 lzma2 delta x86 powerpc ia64 arm armthumb sparc
checking which decoders to build... lzma1 lzma2 delta x86 powerpc ia64 arm armthumb sparc
checking which match finders to build... hc3 hc4 bt2 bt3 bt4
checking which integrity checks to build... crc32 crc64 sha256
checking if assembler optimizations should be used... no
checking if small size is preferred over speed... no
checking if threading support is wanted... no
checking how much RAM to assume if the real amount is unknown... 128 MiB

checking for a shell that conforms to POSIX... /bin/sh

Initializing Automake:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether ln -s works... yes
checking for style of include used by make... GNU
checking for alpha-unknown-linux-gnu-gcc... alpha-unknown-linux-gnu-gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/app-arch/xz-utils-5.0.3/work/xz-5.0.3':
configure: error: C compiler cannot create executables
See `config.log' for more details

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-arch/xz-utils-5.0.3/work/xz-5.0.3/config.log
 * ERROR: app-arch/xz-utils-5.0.3 failed (configure phase):
 *   econf failed
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_configure
 *   environment, line 2214:  Called econf '--enable-nls' '--disable-threads' '--disable-static'
 *     ebuild.sh, line  561:  Called die
 * The specific snippet of code:
 *   			die "econf failed"
 * 
 * If you need support, post the output of 'emerge --info =app-arch/xz-utils-5.0.3',
 * the complete build log and the output of 'emerge -pqv =app-arch/xz-utils-5.0.3'.
 * The complete build log is located at '/var/tmp/portage/app-arch/xz-utils-5.0.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-arch/xz-utils-5.0.3/temp/environment'.
 * S: '/var/tmp/portage/app-arch/xz-utils-5.0.3/work/xz-5.0.3'

 * Messages for package app-arch/xz-utils-5.0.3:
 * ERROR: app-arch/xz-utils-5.0.3 failed (configure phase):
 *   econf failed
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_configure
 *   environment, line 2214:  Called econf '--enable-nls' '--disable-threads' '--disable-static'
 *     ebuild.sh, line  561:  Called die
 * The specific snippet of code:
 *   			die "econf failed"
 * 
 * If you need support, post the output of 'emerge --info =app-arch/xz-utils-5.0.3',
 * the complete build log and the output of 'emerge -pqv =app-arch/xz-utils-5.0.3'.
 * The complete build log is located at '/var/tmp/portage/app-arch/xz-utils-5.0.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-arch/xz-utils-5.0.3/temp/environment'.
 * S: '/var/tmp/portage/app-arch/xz-utils-5.0.3/work/xz-5.0.3'


!!! 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/lib/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/lib/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 '/space/catalyst/tmp/default/stage2-alpha-20111029/.catalyst_lock'



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


Navigation:
Lists: gentoo-releng-autobuilds: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
[alpha-auto] Catalyst fatal build error - stage2.spec
Next by thread:
[ppc64-auto] Catalyst non-fatal build error - installcd-stage1.spec
Previous by date:
[amd64-auto] Catalyst build complete, but with errors
Next by date:
[alpha-auto] Catalyst build error - post_build


Updated Jun 29, 2012

Summary: Archive of the gentoo-releng-autobuilds mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.