* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage1-x32.spec
@ 2014-08-21 8:59 99% catalyst
0 siblings, 0 replies; 1+ results
From: catalyst @ 2014-08-21 8:59 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
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/release/amd64-auto.conf
Setting sharedir to config file value "/usr/lib64/catalyst/"
Setting snapshot_cache to config file value "/release/tmp/snapshots"
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 "autoresume bindist pkgcache preserve_libs seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Preserving libs during unmerge.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: stage1
Building natively for amd64
stage1 root path is /tmp/stage1root
Source path set to /release/buildroot/amd64-dev/builds/default/stage3-x32-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20140821/
The autoresume path is /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-x32-20140821/
stage1 stage path is /release/buildroot/amd64-dev/tmp/default/stage1-x32-20140821/tmp/stage1root
Location of the package cache is /release/buildroot/amd64-dev/packages/default/stage1-x32-20140821/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-x32-20140821/
>>> 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-stage1-x32-20140821/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/default/stage1-x32-20140821/
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 /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-x32-20140821/
Emptying directory /release/buildroot/amd64-dev/tmp/default/stage1-x32-20140821/
Starting tar extract from /release/buildroot/amd64-dev/builds/default/stage3-x32-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/default/stage1-x32-20140821/ (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 /release/buildroot/amd64-dev/tmp/default/stage1-x32-20140821///tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /release/buildroot/amd64-dev/tmp/default/stage1-x32-20140821//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/default/stage1-x32-20140821//tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/default/stage1-x32-20140821/
/usr/lib64/catalyst//targets/support/functions.sh: line 17: 15835 Segmentation fault ${clst_CHROOT} ${chroot_path} .${destdir}/${file_name}
!!! 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/lib64/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/lib64/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....
Full build log at /release/tmp/run/catalyst-auto.10207/log/stage1-x32.log
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2014-08-21 8:59 99% [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage1-x32.spec catalyst
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox