public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@hake.hppa.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [hppa-auto] Catalyst fatal build error - hppa2.0/stage1.spec
Date: Fri, 26 Sep 2014 03:55:10 -0400	[thread overview]
Message-ID: <20140926075504.4E244E08FC@pigeon.gentoo.org> (raw)




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/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to config file value "/usr/local/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/usr/local/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 pkgcache seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: stage1
Building natively for hppa
stage1 root path is /tmp/stage1root
Source path set to /usr/local/catalyst/builds/default/stage3-hppa2.0-latest.tar.bz2
Caching snapshot to /usr/local/catalyst/snapshot_cache/20140926/
The autoresume path is /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20140926/
stage1 stage path is /usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926/tmp/stage1root
Location of the package cache is /usr/local/catalyst/packages/default/stage1-hppa2.0-20140926/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20140926/
>>> 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 /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20140926/
clearing chroot ...
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926/
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 /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20140926/
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926/

Starting tar extract from /usr/local/catalyst/builds/default/stage3-hppa2.0-latest.tar.bz2
to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926/ (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 /usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926///tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926//tmp
copying chroot-functions.sh to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926//tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot /usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --oneshot --nodeps --update sys-apps/portage

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)


Updating seed stage...
emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc
>>> Recording sys-devel/gcc in "world" favorites file...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps sys-apps/baselayout
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/baselayout-2.2 for /tmp/stage1root/
>>> Installing (1 of 1) sys-apps/baselayout-2.2 to /tmp/stage1root/

 * Messages for package sys-apps/baselayout-2.2 merged to /tmp/stage1root/:

 * Initializing /tmp/stage1root/lib as a dir
 * Initializing /tmp/stage1root/usr/lib as a dir
 * Initializing /tmp/stage1root/usr/local/lib as a dir
 * Your system profile has SYMLINK_LIB=no, so that means you need to
 * have these paths configured as follows:
 * directories: /tmp/stage1root/lib /tmp/stage1root/usr/lib /tmp/stage1root/usr/local/lib
 * The ebuild will attempt to fix these, but only for trivial conversions.
 * If things fail, you will need to manually create/move the directories.
 * Converting /tmp/stage1root/lib from a symlink to a dir
 * Converting /tmp/stage1root/usr/lib from a symlink to a dir
 * Converting /tmp/stage1root/usr/local/lib from a symlink to a dir
emerge --quiet --usepkg --buildpkg --newuse --oneshot sys-apps/grep virtual/shadow virtual/pkgconfig sys-devel/binutils app-shells/bash sys-apps/net-tools sys-devel/flex sys-apps/gawk app-arch/xz-utils sys-apps/sed sys-devel/bison sys-devel/patch sys-apps/file app-arch/bzip2 app-arch/tar virtual/package-manager net-misc/rsync sys-devel/automake virtual/editor sys-apps/coreutils sys-devel/make sys-apps/findutils virtual/os-headers sys-apps/makedev app-arch/gzip net-misc/wget sys-apps/which sys-devel/libtool sys-apps/diffutils sys-devel/gettext sys-apps/less sys-apps/baselayout virtual/libc sys-devel/autoconf sys-devel/gnuconfig sys-devel/gcc 
>>> Verifying ebuild manifests
>>> Emerging (1 of 71) sys-libs/zlib-1.2.8-r1 for /tmp/stage1root/
>>> Failed to emerge sys-libs/zlib-1.2.8-r1 for /tmp/stage1root/, Log file:
>>>  '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/build.log'
 * Package:    sys-libs/zlib-1.2.8-r1
 * Repository: gentoo
 * Maintainer: base-system@gentoo.org
 * USE:        build elibc_glibc hppa kernel_linux userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
 * Will copy sources from /var/tmp/portage/sys-libs/zlib-1.2.8-r1/work/zlib-1.2.8
/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/environment: line 2340: /dev/fd/62: No such file or directory
 * You're missing a /dev/fd symlink to /proc/self/fd.
 * Please fix the symlink and check your boot scripts (udev/etc...).
 * ERROR: sys-libs/zlib-1.2.8-r1::gentoo failed (configure phase):
 *   /dev/fd is broken
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_configure
 *   environment, line 3274:  Called multilib-minimal_src_configure
 *   environment, line 2518:  Called multilib_parallel_foreach_abi 'multilib-minimal_abi_src_configure'
 *   environment, line 2824:  Called multibuild_parallel_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *   environment, line 2410:  Called multijob_init ''
 *   environment, line 2473:  Called redirect_alloc_fd 'mj_write_fd' '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/multijob.pipe'
 *   environment, line 3236:  Called die
 * The specific snippet of code:
 *           die "/dev/fd is broken";
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/zlib-1.2.8-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/zlib-1.2.8-r1::gentoo'`.
/usr/lib/portage/bin/isolated-functions.sh: line 195: wait: `/dev/fd is broken': not a pid or valid job spec
 * The complete build log is located at '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/work/zlib-1.2.8'
 * S: '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/work/zlib-1.2.8'

 * Messages for package sys-libs/zlib-1.2.8-r1 merged to /tmp/stage1root/:

 * You're missing a /dev/fd symlink to /proc/self/fd.
 * Please fix the symlink and check your boot scripts (udev/etc...).
 * ERROR: sys-libs/zlib-1.2.8-r1::gentoo failed (configure phase):
 *   /dev/fd is broken
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_configure
 *   environment, line 3274:  Called multilib-minimal_src_configure
 *   environment, line 2518:  Called multilib_parallel_foreach_abi 'multilib-minimal_abi_src_configure'
 *   environment, line 2824:  Called multibuild_parallel_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *   environment, line 2410:  Called multijob_init ''
 *   environment, line 2473:  Called redirect_alloc_fd 'mj_write_fd' '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/multijob.pipe'
 *   environment, line 3236:  Called die
 * The specific snippet of code:
 *           die "/dev/fd is broken";
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/zlib-1.2.8-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/zlib-1.2.8-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/work/zlib-1.2.8'
 * S: '/var/tmp/portage/sys-libs/zlib-1.2.8-r1/work/zlib-1.2.8'

!!! 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/lib/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/lib/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....
lockfile does not exist '/usr/local/catalyst/tmp/default/stage1-hppa2.0-20140926/.catalyst_lock'



Full build log at /tmp/catalyst-auto.4036/log/hppa2.0_stage1.log


             reply	other threads:[~2014-09-26  7:55 UTC|newest]

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