Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Catalyst, version 2.0.9
- Copyright 2003-2008 Gentoo Foundation
- Copyright 2008-2011 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 "/home/release/buildroot/amd64-dev"
- Setting portdir to config file value "/usr/portage"
- Setting distdir to config file value "/usr/portage/distfiles"
- Setting options to config file value "autoresume pkgcache snapcache seedcache kerncache"
- Autoresuming support enabled.
- Kernel cache support enabled.
- Package cache support enabled.
- 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 /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-x32-latest.tar.bz2
- Caching snapshot to /var/tmp/catalyst/snapshot_cache/20120613/
- The autoresume path is /home/release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-amd64-x32-20120613/
- stage1 stage path is /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613/tmp/stage1root
- Location of the package cache is /home/release/buildroot/amd64-dev/packages/default/stage1-amd64-x32-20120613/
- Location of the kerncache is /home/release/buildroot/amd64-dev/kerncache/default/stage1-amd64-x32-20120613/
- Checking for processes running in chroot and killing them.
- Removing AutoResume Points: ...
- Emptying directory /home/release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-amd64-x32-20120613/
- >>> 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 /home/release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-amd64-x32-20120613/
- clearing chroot ...
- Emptying directory /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613/
- clearing package cache ...
- purging the pkgcache ...
- clearing kerncache ...
- purging the 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 /home/release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-amd64-x32-20120613/
- Emptying directory /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613/
- Starting tar extract from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-x32-latest.tar.bz2
- to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613/ (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 make.conf to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613///tmp/stage1root/etc
- copying make.profile to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613///tmp/stage1root/etc
- copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613/tmp/
- copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613/tmp/
- Running stage1-chroot.sh in chroot /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-x32-20120613/
- /usr/lib/catalyst//targets/support/functions.sh: line 27: 18127 Killed ${clst_CHROOT} ${chroot_path}/ /tmp/${file_name}
- !!! catalyst: run script failed.
- Traceback (most recent call last):
- File "modules/generic_stage_target.py", line 1194, 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 207, in build_target
- mytarget.run()
- File "modules/generic_stage_target.py", line 1254, in run
- apply(getattr(self,x))
- File "modules/generic_stage_target.py", line 1199, in run_local
- raise CatalystError,"Stage build aborting due to error."
- CatalystError
- !!! catalyst: Error encountered during run of target stage1
- Catalyst aborting....
Add Comment
Please, Sign In to add comment