From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BD0F31384C3 for ; Sat, 5 Sep 2015 08:23:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9FD4C14209; Sat, 5 Sep 2015 08:23:38 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D414014209 for ; Sat, 5 Sep 2015 08:23:37 +0000 (UTC) Received: from hake (hake.hppa.dev.gentoo.org [IPv6:2001:470:ea4a:1:230:6eff:fe2b:c8d4]) by smtp.gentoo.org (Postfix) with SMTP id 8B0013402A2; Sat, 5 Sep 2015 08:23:35 +0000 (UTC) Received: by hake (sSMTP sendmail emulation); Sat, 05 Sep 2015 04:23:32 -0400 Date: Sat, 05 Sep 2015 04:23:32 -0400 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 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Release Engineering Autobuilds X-BeenThere: gentoo-releng-autobuilds@gentoo.org X-BeenThere: gentoo-releng-autobuilds@lists.gentoo.org Reply-To: gentoo-releng-autobuilds@lists.gentoo.org Message-Id: <20150905082338.9FD4C14209@pigeon.gentoo.org> X-Archives-Salt: 8600f293-cce3-4883-9ec8-7ef13eeb086b X-Archives-Hash: 76b1734e13e70d004675a0e5d4c7fe17 * Messages for package sys-apps/sysvinit-2.88-r7: * The last/lastb/mesg/mountpoint/sulogin/utmpdump/wall tools have been moved to * sys-apps/util-linux. The pidof tool has been moved to sys-process/procps. * Messages for package sys-apps/coreutils-8.23: * 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/pam-1.2.1: * Some software with pre-loaded PAM libraries might experience * warnings or failures related to missing symbols and/or versions * after any update. While unfortunate this is a limit of the * implementation of PAM and the software, and it requires you to * restart the software manually after the update. * * You can get a list of such software running a command like * lsof / | egrep -i 'del.*libpam\.so' * * Alternatively, simply reboot your system. * Messages for package sys-apps/busybox-1.23.1-r1: * Could not locate user configfile, so we will save a default one * You cannot have USE='static pam'. Assuming static is more important. * Your configuration for sys-apps/busybox-1.23.1-r1 has been saved in * /etc/portage/savedconfig/sys-apps/busybox-1.23.1-r1 for your editing pleasure. * You can edit these files by hand and remerge this package with * USE=savedconfig to customise the configuration. * You can rename this file/directory to one of the following for * its configuration to apply to multiple versions: * ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/ * [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}] * Messages for package sys-libs/glibc-2.19-r1: * Defaulting /etc/host.conf:multi to on * Generating all locales; edit /etc/locale.gen to save time/space * Messages for package sys-apps/util-linux-2.25.2-r2: * The mesg/wall/write tools have been disabled due to USE=-tty-helpers. * Messages for package sys-apps/less-478: * lesspipe offers colorization options. Run 'lesspipe -h' for info. * 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/ 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: * Failed to set XATTR_PAX markings -re /var/tmp/portage/sys-devel/gcc-4.8.4/image//usr/libexec/gcc/hppa1.1-unknown-linux-gnu/4.8.4/cc1. * Failed to set XATTR_PAX markings -re /var/tmp/portage/sys-devel/gcc-4.8.4/image//usr/libexec/gcc/hppa1.1-unknown-linux-gnu/4.8.4/cc1plus. * 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 dev-lang/python-2.7.9-r1: * Failed to set XATTR_PAX markings -me python. * Messages for package dev-lang/python-3.4.1: * Failed to set XATTR_PAX markings -me python. * Messages for package net-misc/openssh-6.9_p1-r2: * 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.20.2: * The ebuild phase 'prepare' 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 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-20150904/.catalyst_lock' Full build log at /tmp/catalyst-auto.o0DPqg/log/hppa1.1_stage1.log