From: catalyst@dolphin.ia64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage1.spec
Date: Tue, 14 Jan 2014 19:06:32 +0000 [thread overview]
Message-ID: <20140114190636.435DBE09F3@pigeon.gentoo.org> (raw)
checking for resizeterm... yes
checking for /dev/ptmx... yes
checking for /dev/ptc... no
checking for %lld and %llu printf() format support... yes
checking for %zd printf() format support... yes
checking for socklen_t... yes
checking for broken mbstowcs... no
checking whether ia64-unknown-linux-gnu-gcc -pthread supports computed gotos... yes
checking for --with-computed-gotos... yes
checking for pipe2... yes
checking for build directories... done
configure: creating ./config.status
config.status: creating Makefile.pre
config.status: creating Modules/Setup.config
config.status: creating Misc/python.pc
config.status: creating Modules/ld_so_aix
config.status: creating pyconfig.h
creating Modules/Setup
creating Modules/Setup.local
creating Makefile
* configure has detected that the sem_open function is broken.
* Please ensure that /dev/shm is mounted as a tmpfs with mode 1777.
* ERROR: dev-lang/python-3.2.5-r3::gentoo failed (configure phase):
* Broken sem_open function (bug 496328)
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3709: Called die
* The specific snippet of code:
* die "Broken sem_open function (bug 496328)";
*
* If you need support, post the output of `emerge --info '=dev-lang/python-3.2.5-r3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-lang/python-3.2.5-r3::gentoo'`.
/var/tmp/portage/._portage_reinstall_.z_r7aj/bin/isolated-functions.sh: line 188: wait: `Broken sem_open function (bug 496328)': not a pid or valid job spec
* The complete build log is located at '/var/tmp/portage/dev-lang/python-3.2.5-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-3.2.5-r3/temp/environment'.
* Working directory: '/var/tmp/portage/dev-lang/python-3.2.5-r3/work/ia64-unknown-linux-gnu'
* S: '/var/tmp/portage/dev-lang/python-3.2.5-r3/work/Python-3.2.5'
* Messages for package sys-libs/glibc-2.16.0:
* 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-2013d:
* You do not have TIMEZONE set in /etc/timezone.
* Skipping auto-update of /etc/localtime.
* Messages for package app-portage/portage-utils-0.41:
* /etc/portage/postsync.d/q-reinitialize has been installed for convenience
* If you wish for it to be automatically run at the end of every --sync:
* # chmod +x /etc/portage/postsync.d/q-reinitialize
* Normally this should only take a few seconds to run but file systems
* such as ext3 can take a lot longer. To disable, simply do:
* # chmod -x /etc/portage/postsync.d/q-reinitialize
* Messages for package sys-apps/util-linux-2.22.2:
* The agetty util now clears the terminal by default. You
* might want to add --noclear to your /etc/inittab lines.
* Messages for package sys-devel/gcc-4.7.3-r1:
* If you have issues with packages unable to locate libstdc++.la,
* then try running 'fix_libtool_files.sh' on the old gcc versions.
* You might want to review the GCC upgrade guide when moving between
* major versions (like 4.2 to 4.3):
* http://www.gentoo.org/doc/en/gcc-upgrading.xml
* Messages for package sys-devel/gcc-4.6.3:
* If you have issues with packages unable to locate libstdc++.la,
* then try running 'fix_libtool_files.sh' on the old gcc versions.
* You might want to review the GCC upgrade guide when moving between
* major versions (like 4.2 to 4.3):
* http://www.gentoo.org/doc/en/gcc-upgrading.xml
* Messages for package sys-fs/e2fsprogs-1.42.7:
* No /etc/mtab file, creating one temporarily
* Messages for package sys-apps/coreutils-8.20:
* Make sure you run 'hash -r' in your active shells.
* You should also re-source your shell settings for LS_COLORS
* changes, such as: source /etc/profile
* Messages for package sys-libs/gdbm-1.8.3-r4:
* 32bit systems might have to rebuild all gdbm databases due to
* LFS changes in the gdbm format. You can either delete the db
* and regenerate it from scratch, or use the converter:
* http://bugs.gentoo.org/attachment.cgi?id=215326
*
* See this comment for information on how to use it:
* http://bugs.gentoo.org/299390#c15
*
* You should be able to locate most gdbm db's on your system with:
* find /etc /var -type f -exec file {} + | grep 'GNU dbm 1.x or ndbm database'
*
* You could also try using this helper script:
* http://bugs.gentoo.org/attachment.cgi?id=222581
* Messages for package dev-lang/perl-5.12.4-r1:
* Removing dead symlink /usr/share/man/man1/ptar.1.bz2
* Removing dead symlink /usr/share/man/man1/ptardiff.1.bz2
* Removing dead symlink /usr/share/man/man1/shasum.1.bz2
* Removing dead symlink /usr/share/man/man1/cpan.1.bz2
* Removing dead symlink /usr/share/man/man1/cpanp.1.bz2
* Removing dead symlink /usr/share/man/man1/cpan2dist.1.bz2
* Removing dead symlink /usr/share/man/man1/enc2xs.1.bz2
* Removing dead symlink /usr/share/man/man1/piconv.1.bz2
* Removing dead symlink /usr/share/man/man1/instmodsh.1.bz2
* Removing dead symlink /usr/share/man/man1/xsubpp.1.bz2
* Removing dead symlink /usr/share/man/man1/config_data.1.bz2
* Removing dead symlink /usr/share/man/man1/corelist.1.bz2
* Removing dead symlink /usr/share/man/man1/pod2usage.1.bz2
* Removing dead symlink /usr/share/man/man1/podchecker.1.bz2
* Removing dead symlink /usr/share/man/man1/podselect.1.bz2
* Removing dead symlink /usr/share/man/man1/prove.1.bz2
* Removing dead symlink /usr/share/man/man1/pod2man.1.bz2
* Removing dead symlink /usr/share/man/man1/pod2text.1.bz2
* Messages for package dev-lang/perl-5.16.3:
* UPDATE THE PERL MODULES:
* After updating dev-lang/perl you must reinstall
* the installed perl modules.
* Use: perl-cleaner --all
* Unable to establish //usr/share/man/man1/ptar.1* symlink
* Unable to establish //usr/share/man/man1/ptardiff.1* symlink
* Unable to establish //usr/share/man/man1/ptargrep.1* symlink
* Unable to establish //usr/share/man/man1/shasum.1* symlink
* Unable to establish //usr/share/man/man1/cpan.1* symlink
* Unable to establish //usr/share/man/man1/cpanp.1* symlink
* Unable to establish //usr/share/man/man1/cpan2dist.1* symlink
* Unable to establish //usr/share/man/man1/enc2xs.1* symlink
* Unable to establish //usr/share/man/man1/piconv.1* symlink
* Unable to establish //usr/share/man/man1/instmodsh.1* symlink
* Unable to establish //usr/share/man/man1/xsubpp.1* symlink
* Unable to establish //usr/share/man/man1/zipdetails.1* symlink
* Unable to establish //usr/share/man/man1/json_pp.1* symlink
* Unable to establish //usr/share/man/man1/config_data.1* symlink
* Unable to establish //usr/share/man/man1/corelist.1* symlink
* Unable to establish //usr/share/man/man1/pod2usage.1* symlink
* Unable to establish //usr/share/man/man1/podchecker.1* symlink
* Unable to establish //usr/share/man/man1/podselect.1* symlink
* Unable to establish //usr/share/man/man1/perldoc.1* symlink
* Unable to establish //usr/share/man/man1/prove.1* symlink
* Unable to establish //usr/share/man/man1/pod2man.1* symlink
* Unable to establish //usr/share/man/man1/pod2text.1* symlink
* Unable to establish //usr/share/man/man1/perlpodstyle.1* symlink
* Messages for package dev-lang/python-3.2.5-r3:
* configure has detected that the sem_open function is broken.
* Please ensure that /dev/shm is mounted as a tmpfs with mode 1777.
* ERROR: dev-lang/python-3.2.5-r3::gentoo failed (configure phase):
* Broken sem_open function (bug 496328)
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3709: Called die
* The specific snippet of code:
* die "Broken sem_open function (bug 496328)";
*
* If you need support, post the output of `emerge --info '=dev-lang/python-3.2.5-r3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-lang/python-3.2.5-r3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-lang/python-3.2.5-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-3.2.5-r3/temp/environment'.
* Working directory: '/var/tmp/portage/dev-lang/python-3.2.5-r3/work/ia64-unknown-linux-gnu'
* S: '/var/tmp/portage/dev-lang/python-3.2.5-r3/work/Python-3.2.5'
!!! catalyst: run script failed.
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1235, in run_local
"run script failed.",env=self.env)
File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, 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 226, in build_target
mytarget.run()
File "modules/generic_stage_target.py", line 1295, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1240, 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 '/var/tmp/catalyst/tmp/default/stage1-ia64-20140114/.catalyst_lock'
Full build log at /tmp/catalyst-auto.15522/log/stage1.log
next reply other threads:[~2014-01-14 19:06 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 19:06 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-13 3:35 [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage1.spec catalyst
2020-05-15 4:08 catalyst
2020-05-14 3:46 catalyst
2020-05-13 3:26 catalyst
2020-04-27 3:43 catalyst
2019-10-06 20:06 catalyst
2019-10-04 20:03 catalyst
2019-09-27 3:11 catalyst
2019-09-26 3:12 catalyst
2019-09-25 3:12 catalyst
2019-09-24 3:11 catalyst
2019-09-23 3:11 catalyst
2019-09-22 3:14 catalyst
2018-03-15 3:20 catalyst
2018-01-31 3:16 catalyst
2018-01-26 8:13 catalyst
2016-01-19 4:21 catalyst
2015-12-22 5:10 catalyst
2015-12-15 5:04 catalyst
2015-12-08 5:04 catalyst
2015-12-01 5:04 catalyst
2015-03-24 4:56 catalyst
2015-03-17 3:38 catalyst
2015-02-03 4:58 catalyst
2015-01-27 5:06 catalyst
2015-01-20 5:00 catalyst
2014-04-08 3:25 catalyst
2014-01-28 3:44 catalyst
2014-01-21 3:48 catalyst
2014-01-07 18:19 catalyst
2013-12-31 18:21 catalyst
2013-10-08 3:43 catalyst
2013-10-01 7:27 catalyst
2013-08-20 9:07 catalyst
2013-06-25 3:46 catalyst
2013-04-30 6:47 catalyst
2013-04-02 7:16 catalyst
2013-03-05 7:02 catalyst
2013-02-19 3:26 catalyst
2012-11-06 6:22 catalyst
2012-09-11 6:14 catalyst
2012-06-19 3:38 catalyst
2012-05-08 6:29 catalyst
2012-05-01 5:13 catalyst
2012-04-24 3:53 catalyst
2012-04-17 3:34 catalyst
2012-04-10 3:34 catalyst
2012-01-10 6:07 catalyst
2011-11-15 6:18 catalyst
2011-10-11 6:41 catalyst
2011-08-09 3:29 catalyst
2011-08-02 3:28 catalyst
2011-07-26 3:28 catalyst
2011-06-07 6:02 catalyst
2011-04-12 3:45 catalyst
2011-02-01 3:20 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=20140114190636.435DBE09F3@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