public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@timberdoodle.ppc64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ppc64-auto] Catalyst non-fatal build error - installcd-stage2-minimal.spec
Date: Sun, 27 Apr 2014 15:05:45 -0700	[thread overview]
Message-ID: <20140427221039.05303E0968@pigeon.gentoo.org> (raw)




Catalyst, version 2.0.16
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/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to config file value "/var/tmp/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/var/tmp/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 bindist kerncache pkgcache seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Kernel cache support enabled.
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: livecd-stage2
Building natively for powerpc
Caching snapshot to /var/tmp/catalyst/snapshot_cache/20140427/
The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-livecd-stage2-ppc64-20140427/
Location of the package cache is /var/tmp/catalyst/packages/default/livecd-stage2-ppc64-20140427/
Location of the kerncache is /var/tmp/catalyst/kerncache/default/livecd-stage2-ppc64-20140427/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-livecd-stage2-ppc64-20140427/
>>> 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 /var/tmp/catalyst/tmp/default/.autoresume-livecd-stage2-ppc64-20140427/
clearing chroot ...
Emptying directory /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/
clearing package cache ...
purging the pkgcache ...
clearing kerncache ...
purging the kerncache ...
--- Running action sequence: unpack

Starting rsync from /var/tmp/catalyst/tmp/default/livecd-stage1-ppc64-32ul-20140427/
to /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/ (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: 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
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to ./tmp
copying pre-kmerge.sh to /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/./tmp
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/./tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Emerging (1 of 2) app-arch/cpio-2.11-r1
>>> Installing (1 of 2) app-arch/cpio-2.11-r1
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.45.1
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.45.1

 * Messages for package sys-kernel/genkernel-3.4.45.1:

 * Copying files to /var/cache/genkernel/src...
 * Documentation is available in the genkernel manual page
 * as well as the following URL:
 * http://www.gentoo.org/doc/en/genkernel.xml
 * This package is known to not work with reiser4.  If you are running
 * reiser4 and have a problem, do not file a bug.  We know it does not
 * work and we don't plan on fixing it since reiser4 is the one that is
 * broken in this regard.  Try using a sane filesystem like ext3 or
 * even reiser3.
 * The LUKS support has changed from versions prior to 3.4.4.  Now,
 * you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
 * Local use flag 'crypt' has been renamed to 'cryptsetup' (bug #414523).
 * Please set flag 'cryptsetup' for this very package if you would like
 * to have genkernel create an initramfs with LUKS support.
 * Sorry for the inconvenience.
removing /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/./tmp/pre-kmerge.sh from the chroot
removing /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/./tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to ./tmp
copying kmerge.sh to /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/./tmp
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/./tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.45.1 found ... continuing
emerge --quiet --update --newuse sys-kernel/gentoo-sources
[ebuild  N    ] sys-libs/ncurses-5.9-r2 to /tmp/kerncache/ibmpower/
[ebuild  N    ] virtual/libintl-0 to /tmp/kerncache/ibmpower/
[ebuild  N    ] app-arch/bzip2-1.0.6-r6 to /tmp/kerncache/ibmpower/
[ebuild  N    ] sys-libs/zlib-1.2.8-r1 to /tmp/kerncache/ibmpower/
[ebuild  N    ] sys-libs/readline-6.2_p1 to /tmp/kerncache/ibmpower/
[ebuild  N    ] sys-devel/make-3.82-r4 to /tmp/kerncache/ibmpower/
[ebuild  N    ] app-shells/bash-4.2_p45 to /tmp/kerncache/ibmpower/
[ebuild  N    ] sys-apps/util-linux-2.22.2 to /tmp/kerncache/ibmpower/
[ebuild  N    ] sys-apps/hwids-20130915.1 to /tmp/kerncache/ibmpower/
[ebuild  N    ] sys-devel/bc-1.06.95 to /tmp/kerncache/ibmpower/
[ebuild  N    ] sys-fs/udev-208 to /tmp/kerncache/ibmpower/
[ebuild  N    ] virtual/udev-208-r1 to /tmp/kerncache/ibmpower/
[ebuild  N    ] virtual/dev-manager-0 to /tmp/kerncache/ibmpower/
[ebuild  N    ] dev-lang/perl-5.16.3 to /tmp/kerncache/ibmpower/
[ebuild  N    ] app-admin/perl-cleaner-2.7 to /tmp/kerncache/ibmpower/
[ebuild  N    ] sys-kernel/gentoo-sources-3.10.25 to /tmp/kerncache/ibmpower/

The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by sys-fs/udev-208
# required by virtual/udev-208-r1
# required by virtual/dev-manager-0
# required by sys-kernel/gentoo-sources-3.10.25
# required by sys-kernel/gentoo-sources (argument)
=sys-apps/hwids-20130915.1 udev

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.

!!! catalyst: Runscript kernel build failed


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1427, in build_kernel
    self._build_kernel(kname=kname)
  File "modules/generic_stage_target.py", line 1471, in _build_kernel
    "Runscript kernel build failed",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, in cmd
    raise CatalystError,myexc
CatalystError
None

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

Traceback (most recent call last):
File "/usr/lib/catalyst/catalyst", line 218, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1303, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1432, in build_kernel
    "build aborting due to kernel build error."
CatalystError
!!! catalyst: Error encountered during run of target livecd-stage2
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/livecd-stage2-ppc64-20140427/.catalyst_lock'



Full build log at /tmp/catalyst-auto.3036/log/installcd-stage2-minimal.log


             reply	other threads:[~2014-04-27 22:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-27 22:05 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-22 22:55 [gentoo-releng-autobuilds] [ppc64-auto] Catalyst non-fatal build error - installcd-stage2-minimal.spec catalyst
2014-06-15 22:37 catalyst
2014-06-08 22:27 catalyst
2014-06-01 22:40 catalyst
2014-05-25 22:16 catalyst
2014-05-18 22:44 catalyst
2014-05-04 22:18 catalyst
2014-04-20 23:00 catalyst
2014-04-13 23:05 catalyst
2014-04-06 22:22 catalyst
2014-03-30 21:58 catalyst
2014-03-16 21:50 catalyst
2014-03-09 22:41 catalyst
2014-03-02 22:47 catalyst
2014-02-23 23:06 catalyst
2014-02-16 22:59 catalyst
2014-02-09 23:08 catalyst
2013-08-25 21:55 catalyst
2011-11-03  9:21 catalyst
2011-07-04  5:42 catalyst
2011-03-21  7:33 catalyst
2011-02-28  7:35 catalyst
2011-02-14 18:01 catalyst
2011-02-07  6:40 catalyst
2011-01-31  6:45 catalyst
2011-01-24  6:26 catalyst

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140427221039.05303E0968@pigeon.gentoo.org \
    --to=catalyst@timberdoodle.ppc64.dev.gentoo.org \
    --cc=gentoo-releng-autobuilds@lists.gentoo.org \
    --cc=releng@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox