From: catalyst@lantean.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage2.spec
Date: Thu, 13 Aug 2015 12:20:31 +0000 (UTC) [thread overview]
Message-ID: <20150813122031.90A0BE0067@lantean.jmbsvicetto.name> (raw)
Catalyst, version 2.0.18
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 "/home/release/tmp/snapshots"
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 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: stage2
Building natively for amd64
Source path set to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150813/tmp/stage1root/
If this is not desired, remove this directory or turn of seedcache in the options of catalyst.conf
the source path will then be /home/release/buildroot/amd64-dev/builds/default/stage1-amd64-20150813.tar.bz2
Caching snapshot to /home/release/tmp/snapshots/20150813/
The autoresume path is /home/release/buildroot/amd64-dev/tmp/default/.autoresume-stage2-amd64-20150813/
Location of the package cache is /home/release/buildroot/amd64-dev/packages/default/stage2-amd64-20150813/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /home/release/buildroot/amd64-dev/tmp/default/.autoresume-stage2-amd64-20150813/
>>> 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-stage2-amd64-20150813/
clearing chroot ...
Emptying directory /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20150813/
clearing package cache ...
purging the pkgcache ...
clearing kerncache ...
--- Running action sequence: unpack
Starting rsync from /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150813/tmp/stage1root/
to /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20150813/ (This may take some time) ...
--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: setup_confdir
Configuring /etc/portage...
--- 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 stage2-chroot.sh to /tmp
copying stage2-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20150813//tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20150813//tmp
Ensure the file has the executable bit set
Running stage2-chroot.sh in chroot /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20150813/
>>> Regenerating /etc/ld.so.cache...
^[[m\x0f^[[1m^[[32mGentoo Linux; ^[[m\x0f^[[1m^[[34mhttp://www.gentoo.org/^[[m\x0f
Copyright 1999-$ Gentoo Foundation; Distributed under the GPLv2
-------------------------------------------------------------------------------
[[ (0/3) Locating packages ]]
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using baselayout : >=sys-apps/baselayout-2
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using portage : portage
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using os-headers : >=sys-kernel/linux-headers-3.18
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using binutils : sys-devel/binutils
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using gcc : sys-devel/gcc
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using gettext : gettext
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using libc : virtual/libc
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using texinfo : sys-apps/texinfo
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using zlib : zlib
^[[m\x0f^[[1m^[[32m*^[[m\x0f Using ncurses : ncurses
-------------------------------------------------------------------------------
[[ (1/3) Configuring environment ]]
-------------------------------------------------------------------------------
[[ (2/3) Updating portage ]]
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.2.20.1::gentoo
>>> Installing (1 of 1) sys-apps/portage-2.2.20.1::gentoo
* Messages for package sys-apps/portage-2.2.20.1:
* Could not find a UTF-8 locale. This may trigger build failures in
* some python packages. Please ensure that a UTF-8 locale is listed in
* /etc/locale.gen and run locale-gen.
-------------------------------------------------------------------------------
[[ (3/3) Emerging packages ]]
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-devel/gcc-4.8.4
>>> Emerging (1 of 14) sys-libs/zlib-1.2.8-r1::gentoo
>>> Failed to emerge sys-libs/zlib-1.2.8-r1, Log file:
>>> '/var/log/portage/sys-libs:zlib-1.2.8-r1:20150813-122029.log'
* Package: sys-libs/zlib-1.2.8-r1
* Repository: gentoo
* USE: abi_x86_64 amd64 bootstrap elibc_glibc 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
* abi_x86_64.amd64: copying to /var/tmp/portage/sys-libs/zlib-1.2.8-r1/work/zlib-1.2.8-abi_x86_64.amd64
* abi_x86_64.amd64: running multilib-minimal_abi_src_configure
/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/environment: /usr/share/gnuconfig/config.sub: /bin/sh: bad interpreter: No such file or directory
./configure --shared --prefix=/usr --libdir=/usr/lib64
/var/tmp/portage/sys-libs/zlib-1.2.8-r1/temp/environment: ./configure: /bin/sh: bad interpreter: No such file or directory
* ERROR: sys-libs/zlib-1.2.8-r1::gentoo failed (configure phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3207: Called multilib-minimal_src_configure
* environment, line 2473: Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
* environment, line 2680: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 2404: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 2402: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
* environment, line 565: Called multilib-minimal_abi_src_configure
* environment, line 2467: Called multilib_src_configure
* environment, line 2911: Called die
* The specific snippet of code:
* echoit ./configure --shared --prefix="${EPREFIX}/usr" --libdir="${EPREFIX}/usr/$(get_libdir)" ${uname:+--uname=${uname}} || die
*
* 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/log/portage/sys-libs:zlib-1.2.8-r1:20150813-122029.log'.
* For convenience, a symlink to the 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-abi_x86_64.amd64'
* 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:
* ERROR: sys-libs/zlib-1.2.8-r1::gentoo failed (configure phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3207: Called multilib-minimal_src_configure
* environment, line 2473: Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
* environment, line 2680: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 2404: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 2402: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
* environment, line 565: Called multilib-minimal_abi_src_configure
* environment, line 2467: Called multilib_src_configure
* environment, line 2911: Called die
* The specific snippet of code:
* echoit ./configure --shared --prefix="${EPREFIX}/usr" --libdir="${EPREFIX}/usr/$(get_libdir)" ${uname:+--uname=${uname}} || die
*
* 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/log/portage/sys-libs:zlib-1.2.8-r1:20150813-122029.log'.
* For convenience, a symlink to the 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-abi_x86_64.amd64'
* 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 1253, 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 1333, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1258, in run_local
raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage2
Catalyst aborting....
lockfile does not exist '/home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20150813/.catalyst_lock'
Full build log at /home/release/tmp/run/catalyst-auto.rusBWH/log/stage2.log
next reply other threads:[~2015-08-13 12:20 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 12:20 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-17 22:11 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage2.spec catalyst
2020-06-14 22:13 catalyst
2020-05-11 16:26 catalyst
2020-02-03 1:07 catalyst
2019-07-22 3:59 catalyst
2019-07-16 11:16 catalyst
2019-07-16 0:53 catalyst
2018-08-14 16:27 catalyst
2017-12-26 21:58 catalyst
2017-12-24 21:59 catalyst
2017-12-23 3:45 catalyst
2017-12-21 21:58 catalyst
2017-12-19 21:54 catalyst
2017-12-17 22:45 catalyst
2017-12-15 7:26 catalyst
2017-12-03 21:10 catalyst
2017-12-03 20:46 catalyst
2017-12-03 20:40 catalyst
2017-10-26 3:25 catalyst
2015-11-21 19:17 catalyst
2015-11-16 5:10 catalyst
2015-11-09 5:04 catalyst
2015-11-02 5:07 catalyst
2015-11-01 5:30 catalyst
2015-10-30 2:31 catalyst
2015-10-29 22:43 catalyst
2015-10-29 4:15 catalyst
2015-10-26 4:28 catalyst
2015-10-24 2:11 catalyst
2015-10-23 5:26 catalyst
2015-08-29 17:43 catalyst
2015-08-29 17:29 catalyst
2015-08-29 17:17 catalyst
2015-08-29 11:23 catalyst
2015-08-29 2:55 catalyst
2015-08-29 2:52 catalyst
2015-08-29 2:45 catalyst
2015-06-16 2:35 catalyst
2015-06-08 5:05 catalyst
2015-05-11 4:58 catalyst
2015-02-23 4:24 catalyst
2014-11-24 4:35 catalyst
2014-11-17 4:45 catalyst
2011-03-31 4:35 catalyst
2011-03-24 5:19 catalyst
2011-03-10 5:40 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=20150813122031.90A0BE0067@lantean.jmbsvicetto.name \
--to=catalyst@lantean.jmbsvicetto.name \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=jmbsvicetto@gmail.com \
/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