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, 11 Dec 2015 08:30:26 -0500 [thread overview]
Message-ID: <20151211133030.E0F4221C020@pigeon.gentoo.org> (raw)
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa2.0-20151211/
clearing chroot ...
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa2.0-20151211/
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-20151211/
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa2.0-20151211/
Starting tar extract from /usr/local/catalyst/builds/default/stage3-hppa2.0-latest.tar.bz2
to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20151211/ (This may take some time) ...
tar: XATTR support is not available
tar: SELinux support is not available
--- 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-20151211///tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20151211//tmp
copying chroot-functions.sh to /usr/local/catalyst/tmp/default/stage1-hppa2.0-20151211//tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot /usr/local/catalyst/tmp/default/stage1-hppa2.0-20151211/
>>> Regenerating /etc/ld.so.cache...
Adding USE=' build' to make.conf for portage build
emerge --quiet --oneshot --update --newuse sys-apps/portage
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
>>> Verifying ebuild manifests
>>> Emerging (1 of 6) sys-apps/install-xattr-0.5::gentoo
>>> Installing (1 of 6) sys-apps/install-xattr-0.5::gentoo
>>> Emerging (2 of 6) dev-python/packaging-15.3-r2::gentoo
>>> Installing (2 of 6) dev-python/packaging-15.3-r2::gentoo
>>> Emerging (3 of 6) dev-python/setuptools-18.4::gentoo
>>> Installing (3 of 6) dev-python/setuptools-18.4::gentoo
>>> Emerging (4 of 6) dev-python/certifi-2015.11.20::gentoo
>>> Installing (4 of 6) dev-python/certifi-2015.11.20::gentoo
>>> Emerging (5 of 6) dev-python/pyxattr-0.5.3::gentoo
>>> Installing (5 of 6) dev-python/pyxattr-0.5.3::gentoo
>>> Emerging (6 of 6) sys-apps/portage-2.2.24::gentoo
>>> Installing (6 of 6) sys-apps/portage-2.2.24::gentoo
* Messages for package dev-python/packaging-15.3-r2:
* 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.
* Messages for package dev-python/setuptools-18.4:
* 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.
* Messages for package dev-python/certifi-2015.11.20:
* 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.
* Messages for package dev-python/pyxattr-0.5.3:
* 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.
* Messages for package sys-apps/portage-2.2.24:
* 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.
Updating seed stage...
emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-devel/gcc-4.9.3
>>> Running pre-merge checks for sys-devel/gcc-4.8.5
>>> Emerging (1 of 43) sys-libs/glibc-2.21-r1::gentoo
>>> Installing (1 of 43) sys-libs/glibc-2.21-r1::gentoo
>>> Emerging (2 of 43) virtual/libintl-0-r2::gentoo
>>> Installing (2 of 43) virtual/libintl-0-r2::gentoo
>>> Emerging (3 of 43) sys-libs/timezone-data-2015f::gentoo
>>> Installing (3 of 43) sys-libs/timezone-data-2015f::gentoo
>>> Emerging (4 of 43) dev-lang/python-exec-2.0.1-r1::gentoo
>>> Installing (4 of 43) dev-lang/python-exec-2.0.1-r1::gentoo
>>> Emerging (5 of 43) dev-libs/gmp-6.0.0a::gentoo
>>> Failed to emerge dev-libs/gmp-6.0.0a, Log file:
>>> '/var/tmp/portage/dev-libs/gmp-6.0.0a/temp/build.log'
* Package: dev-libs/gmp-6.0.0a
* Repository: gentoo
* Maintainer: toolchain@gentoo.org
* USE: cxx elibc_glibc hppa kernel_linux userland_GNU
* FEATURES: preserve-libs sandbox userpriv usersandbox
xz: Cannot establish signal handlers
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
* ERROR: dev-libs/gmp-6.0.0a::gentoo failed (unpack phase):
* unpack: failure unpacking gmp-6.0.0a.tar.xz
*
* Call stack:
* ebuild.sh, line 90: Called src_unpack
* environment, line 2841: Called default
* phase-functions.sh, line 763: Called default_src_unpack
* phase-functions.sh, line 790: Called __eapi0_src_unpack
* phase-helpers.sh, line 736: Called unpack 'gmp-6.0.0a.tar.xz'
* phase-helpers.sh, line 509: Called __unpack_tar 'xz -d'
* phase-helpers.sh, line 317: Called __assert_sigpipe_ok 'unpack: failure unpacking gmp-6.0.0a.tar.xz'
* isolated-functions.sh, line 41: Called __helpers_die 'unpack: failure unpacking gmp-6.0.0a.tar.xz'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=dev-libs/gmp-6.0.0a::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-libs/gmp-6.0.0a::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-libs/gmp-6.0.0a/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/gmp-6.0.0a/temp/environment'.
* Working directory: '/var/tmp/portage/dev-libs/gmp-6.0.0a/work'
* S: '/var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0'
* Messages for package sys-libs/glibc-2.21-r1:
* Defaulting /etc/host.conf:multi to on
* Generating all locales; edit /etc/locale.gen to save time/space
* Messages for package sys-libs/timezone-data-2015f:
* You do not have TIMEZONE set in /etc/timezone.
* Skipping auto-update of /etc/localtime.
* Messages for package dev-libs/gmp-6.0.0a:
* ERROR: dev-libs/gmp-6.0.0a::gentoo failed (unpack phase):
* unpack: failure unpacking gmp-6.0.0a.tar.xz
*
* Call stack:
* ebuild.sh, line 90: Called src_unpack
* environment, line 2841: Called default
* phase-functions.sh, line 763: Called default_src_unpack
* phase-functions.sh, line 790: Called __eapi0_src_unpack
* phase-helpers.sh, line 736: Called unpack 'gmp-6.0.0a.tar.xz'
* phase-helpers.sh, line 509: Called __unpack_tar 'xz -d'
* phase-helpers.sh, line 317: Called __assert_sigpipe_ok 'unpack: failure unpacking gmp-6.0.0a.tar.xz'
* isolated-functions.sh, line 41: Called __helpers_die 'unpack: failure unpacking gmp-6.0.0a.tar.xz'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=dev-libs/gmp-6.0.0a::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-libs/gmp-6.0.0a::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-libs/gmp-6.0.0a/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/gmp-6.0.0a/temp/environment'.
* Working directory: '/var/tmp/portage/dev-libs/gmp-6.0.0a/work'
* S: '/var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0'
!!! 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-20151211/.catalyst_lock'
Full build log at /tmp/catalyst-auto.tbr9hy/log/hppa2.0_stage1.log
next reply other threads:[~2015-12-11 13:30 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:30 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-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-26 7:55 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=20151211133030.E0F4221C020@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