public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@dolphin.ia64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst non-fatal build error - installcd-stage1.spec
Date: Tue, 29 Nov 2011 23:56:52 +0000	[thread overview]
Message-ID: <20111129235607.9AA3721C04B@pigeon.gentoo.org> (raw)




Catalyst, version 2.0.7.1
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/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 ccache kerncache metadata_overlay pkgcache seedcache snapcache"
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: livecd-stage1
Building natively for ia64
Source path set to /var/tmp/catalyst/tmp/default/stage3-ia64-20111129/
	If this is not desired, remove this directory or turn off
	seedcache in the options of catalyst.conf the source path
	will then be /var/tmp/catalyst/builds/default/stage3-ia64-20111129.tar.bz2

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

Starting rsync from /var/tmp/catalyst/tmp/default/stage3-ia64-20111129/
to /var/tmp/catalyst/tmp/default/livecd-stage1-ia64-20111129/ (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


Warning!!!  
	The use of -* in livecd/use will cause portage to ignore
	package.use in the profile and portage_confdir. You've been warned!
--- Running action sequence: setup_environment
--- Running action sequence: build_packages
copying livecd-stage1-chroot.sh to /var/tmp/catalyst/tmp/default/livecd-stage1-ia64-20111129/tmp/
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/livecd-stage1-ia64-20111129/tmp/
Running livecd-stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/livecd-stage1-ia64-20111129/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps --noreplace dev-util/ccache
>>> 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
 * Maintainer: robbat2@gentoo.org toolchain@gentoo.org
 * USE:        elibc_glibc ia64 kernel_linux 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 ...
 [ !! ]

 * Failed Running autoconf !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-util/ccache-2.4-r9/temp/autoconf.out

 * ERROR: dev-util/ccache-2.4-r9 failed (unpack phase):
 *   Failed Running autoconf !
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_unpack
 *   environment, line 2813:  Called eautoconf
 *   environment, line  814:  Called autotools_run_tool 'autoconf'
 *   environment, line  469:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * 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:
 * Failed Running autoconf !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-util/ccache-2.4-r9/temp/autoconf.out
 * ERROR: dev-util/ccache-2.4-r9 failed (unpack phase):
 *   Failed Running autoconf !
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_unpack
 *   environment, line 2813:  Called eautoconf
 *   environment, line  814:  Called autotools_run_tool 'autoconf'
 *   environment, line  469:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * 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'


!!! catalyst: Error in attempt to build packages


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1362, in build_packages
    "Error in attempt to build packages",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: livecdbuild 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 1367, in build_packages
    "build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target livecd-stage1
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/livecd-stage1-ia64-20111129/.catalyst_lock'



Full build log at /tmp/catalyst-auto.18407/log/installcd-stage1.log



             reply	other threads:[~2011-11-29 23:56 UTC|newest]

Thread overview: 147+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 23:56 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-26  7:09 [gentoo-releng-autobuilds] [ia64-auto] Catalyst non-fatal build error - installcd-stage1.spec catalyst
2024-04-19  9:59 catalyst
2024-04-12  9:39 catalyst
2023-06-07  5:45 catalyst
2023-05-31 21:43 catalyst
2023-05-17  7:20 catalyst
2023-05-10  6:27 catalyst
2023-05-03 19:28 catalyst
2020-05-12  4:56 catalyst
2020-05-11  5:03 catalyst
2020-05-10  6:03 catalyst
2020-05-09  4:38 catalyst
2020-05-08 17:53 catalyst
2020-04-30  5:15 catalyst
2020-04-29  4:57 catalyst
2020-04-28  5:04 catalyst
2020-04-26  5:14 catalyst
2020-04-25  6:50 catalyst
2020-01-13  5:45 catalyst
2020-01-12  5:01 catalyst
2019-10-05  6:47 catalyst
2019-10-01  6:22 catalyst
2019-05-12 18:15 catalyst
2019-05-11 18:31 catalyst
2019-05-10 16:51 catalyst
2019-05-09 16:53 catalyst
2019-05-08 20:26 catalyst
2019-05-07 16:58 catalyst
2019-05-06 16:52 catalyst
2019-05-05 17:04 catalyst
2019-05-03 16:56 catalyst
2019-05-02 20:01 catalyst
2018-06-17 13:48 catalyst
2018-06-16 14:02 catalyst
2018-06-14 13:54 catalyst
2018-06-13 13:49 catalyst
2018-06-12 14:33 catalyst
2018-06-11 14:05 catalyst
2018-06-10 14:45 catalyst
2018-06-09 14:56 catalyst
2018-06-08 13:50 catalyst
2018-06-07 13:56 catalyst
2018-06-06 13:52 catalyst
2018-06-05 13:50 catalyst
2018-06-04 16:10 catalyst
2018-06-03 15:45 catalyst
2018-06-02 14:02 catalyst
2018-06-01 14:04 catalyst
2018-05-31 14:59 catalyst
2018-05-30 14:11 catalyst
2018-05-29 14:02 catalyst
2018-05-28 14:08 catalyst
2018-05-27 13:59 catalyst
2018-05-26 13:59 catalyst
2018-05-25 14:06 catalyst
2018-05-24 17:53 catalyst
2018-05-23 13:58 catalyst
2018-05-21 13:57 catalyst
2018-05-20 14:01 catalyst
2018-03-16 15:40 catalyst
2018-03-14 14:04 catalyst
2016-03-22 14:46 catalyst
2016-03-15 13:05 catalyst
2016-03-08 12:52 catalyst
2016-03-01 16:02 catalyst
2016-01-05 12:48 catalyst
2015-12-29 22:27 catalyst
2015-11-24 12:08 catalyst
2015-11-17 11:55 catalyst
2015-11-10 12:03 catalyst
2015-11-03 13:08 catalyst
2015-10-27 13:02 catalyst
2015-10-20 11:50 catalyst
2015-10-13 12:01 catalyst
2015-10-06 11:57 catalyst
2015-09-29 15:12 catalyst
2015-09-22 14:48 catalyst
2015-09-15 14:45 catalyst
2015-09-08 14:52 catalyst
2015-08-04 14:00 catalyst
2015-07-28 17:10 catalyst
2015-07-21 13:00 catalyst
2015-07-14 11:41 catalyst
2015-07-07 11:38 catalyst
2015-06-30 11:28 catalyst
2015-06-23 11:23 catalyst
2015-06-16 11:23 catalyst
2015-06-09 11:31 catalyst
2015-06-02 12:28 catalyst
2015-05-26 11:32 catalyst
2015-05-19 11:29 catalyst
2015-05-12 12:52 catalyst
2015-05-05 12:49 catalyst
2015-04-28 12:10 catalyst
2015-04-21 11:38 catalyst
2015-04-07 11:03 catalyst
2015-03-31 12:51 catalyst
2015-03-10 11:07 catalyst
2015-03-03 11:07 catalyst
2015-02-17 11:59 catalyst
2015-02-10 11:16 catalyst
2015-01-13 14:38 catalyst
2015-01-06 12:24 catalyst
2014-12-30 11:35 catalyst
2014-12-23 11:39 catalyst
2014-12-16 11:33 catalyst
2014-12-09 11:31 catalyst
2014-12-02 11:43 catalyst
2014-11-25 11:26 catalyst
2014-11-18 11:57 catalyst
2014-11-11 11:48 catalyst
2014-11-04 11:12 catalyst
2014-10-28 11:14 catalyst
2014-09-09 12:30 catalyst
2014-08-19 11:13 catalyst
2014-08-12 11:43 catalyst
2014-08-05 13:28 catalyst
2014-01-30 18:51 catalyst
2013-12-18 14:20 catalyst
2013-11-06 13:11 catalyst
2013-08-14  6:13 catalyst
2013-01-09  5:15 catalyst
2012-12-12  0:55 catalyst
2012-12-05  0:51 catalyst
2012-11-28  0:51 catalyst
2012-11-21  0:50 catalyst
2012-11-14  0:51 catalyst
2012-08-29  2:24 catalyst
2012-08-22 11:47 catalyst
2012-08-15 11:42 catalyst
2012-08-08  7:13 catalyst
2012-08-01  4:37 catalyst
2012-04-04  1:23 catalyst
2012-02-01  0:48 catalyst
2012-01-25  0:48 catalyst
2012-01-18  0:14 catalyst
2012-01-04  0:26 catalyst
2011-12-28  1:38 catalyst
2011-12-21  0:30 catalyst
2011-12-14  1:39 catalyst
2011-12-06 23:57 catalyst
2011-08-16 23:33 catalyst
2011-07-19 23:29 catalyst
2011-05-03 22:58 catalyst
2011-04-27  1:27 catalyst
2011-04-05 23:30 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=20111129235607.9AA3721C04B@pigeon.gentoo.org \
    --to=catalyst@dolphin.ia64.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