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 - hppa1.1/stage1.spec
Date: Sat, 18 Jul 2015 04:23:02 -0400	[thread overview]
Message-ID: <20150718082308.72F9CE080B@pigeon.gentoo.org> (raw)





 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.

 * Messages for package sys-apps/openrc-0.17:

 * Auto-adding 'binfmt' service to your boot runlevel
 * Setting the console font does not work on all HPPA consoles.
 * You can still enable it by running:
 * # rc-update add consolefont boot
 * In this version of OpenRC, the loopback interface no longer
 * satisfies the net virtual.
 * If you have services now which do not start because of this,
 * They can be fixed by adding rc_need="!net"
 * to the /etc/conf.d/<servicename> file.
 * You should also file a bug against the service asking that
 * need net be dropped from the dependencies.
 * The bug you file should block the following tracker:
 * https://bugs.gentoo.org/show_bug.cgi?id=439092
 * 
 * Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not
 * fixed correctly in earlier versions of OpenRC.
 * The correct fix is implemented in this version, but that
 * means netmount needs to be added to the default runlevel if
 * you are using nfs file systems.
 * 
 * You should now update all files in /etc, using etc-update
 * or equivalent before restarting any services or this host.

 * Messages for package sys-devel/gcc-4.8.4:

 * 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 net-misc/openssh-6.7_p1:

 * dev-libs/openssl was built with 'bindist' - disabling ecdsa support
 * Remember to merge your config files in /etc/ssh/ and then
 * reload sshd: '/etc/init.d/sshd reload'.
 * Note: openssh-6.7 versions no longer support USE=tcpd as upstream has
 *       dropped it.  Make sure to update any configs that you might have.

 * Messages for package dev-lang/perl-5.18.2-r2:

 * 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/ptargrep.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/bin/cpanp
 * Removing dead symlink //usr/share/man/man1/cpanp.1.bz2
 * Removing dead symlink //usr/bin/cpan2dist
 * Removing dead symlink //usr/share/man/man1/cpan2dist.1.bz2
 * Removing dead symlink //usr/bin/cpanp-run-perl
 * 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/zipdetails.1.bz2
 * Removing dead symlink //usr/share/man/man1/json_pp.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/perldoc.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
 * Removing dead symlink //usr/share/man/man1/perlpodstyle.1.bz2

 * Messages for package dev-lang/perl-5.20.2:

 * 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/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-libs/libxml2-2.9.2-r1:

 * The ebuild phase 'compile' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
Traceback (most recent call last):
  File "/usr/lib/python-exec/python2.7/emerge", line 50, in <module>
    retval = emerge_main()
  File "/usr/lib/python2.7/site-packages/_emerge/main.py", line 1154, in emerge_main
    return run_action(emerge_config)
  File "/usr/lib/python2.7/site-packages/_emerge/actions.py", line 3191, in run_action
    emerge_config.args, spinner)
  File "/usr/lib/python2.7/site-packages/_emerge/actions.py", line 498, in action_build
    retval = mergetask.merge()
  File "/usr/lib/python2.7/site-packages/_emerge/Scheduler.py", line 1028, in merge
    rval = self._merge()
  File "/usr/lib/python2.7/site-packages/_emerge/Scheduler.py", line 1430, in _merge
    self._main_loop()
  File "/usr/lib/python2.7/site-packages/_emerge/Scheduler.py", line 1401, in _main_loop
    self._event_loop.iteration()
  File "/usr/lib/python2.7/site-packages/portage/util/_eventloop/EventLoop.py", line 204, in iteration
    if self._run_timeouts():
  File "/usr/lib/python2.7/site-packages/portage/util/_eventloop/EventLoop.py", line 468, in _run_timeouts
    if self._run_idle_callbacks():
  File "/usr/lib/python2.7/site-packages/portage/util/_eventloop/EventLoop.py", line 430, in _run_idle_callbacks
    if not x.callback(*x.args):
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 74, in _async_wait_cb
    self.wait()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait
    self._wait_hook()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook
    self._exit_listener_stack.pop()(self)
  File "/usr/lib/python2.7/site-packages/_emerge/EbuildPhase.py", line 345, in _die_hooks_exit
    self.wait()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait
    self._wait_hook()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook
    self._exit_listener_stack.pop()(self)
  File "/usr/lib/python2.7/site-packages/_emerge/TaskSequence.py", line 47, in _task_exit_handler
    self.wait()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait
    self._wait_hook()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook
    self._exit_listener_stack.pop()(self)
  File "/usr/lib/python2.7/site-packages/_emerge/CompositeTask.py", line 134, in _default_final_exit
    return self.wait()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait
    self._wait_hook()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook
    self._exit_listener_stack.pop()(self)
  File "/usr/lib/python2.7/site-packages/_emerge/EbuildBuild.py", line 298, in _build_exit
    self._unlock_builddir()
  File "/usr/lib/python2.7/site-packages/_emerge/EbuildBuild.py", line 294, in _unlock_builddir
    self._build_dir.unlock()
  File "/usr/lib/python2.7/site-packages/_emerge/EbuildBuildDir.py", line 96, in unlock
    catdir_lock.start()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousTask.py", line 30, in start
    self._start()
  File "/usr/lib/python2.7/site-packages/_emerge/AsynchronousLock.py", line 47, in _start
    wantnewlockfile=True, flags=os.O_NONBLOCK)
  File "/usr/lib/python2.7/site-packages/portage/locks.py", line 102, in lockfile
    raise DirectoryNotFound(os.path.dirname(mypath))
DirectoryNotFound: /var/tmp/portage

!!! 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-hppa1.1-20150717/.catalyst_lock'



Full build log at /tmp/catalyst-auto.2Ix5Gh/log/hppa1.1_stage1.log


             reply	other threads:[~2015-07-18  8:23 UTC|newest]

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