[gentoo-releng-autobuilds] [hppa-auto] Catalyst fatal build error - hppa1.1/stage1.spec

# Name of the PIC object.
pic_object=$write_lobj

# Name of the non-PIC object
non_pic_object=$write_oldobj

EOF

mv: cannot stat 'cp-demangle.loT': No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/bin/bash ../libtool --tag CXX --tag disable-shared   --mode=link /var/tmp/portage/sys-devel/gcc-4.8.4/work/build/./gcc/xgcc -shared-libgcc -B/var/tmp/portage/sys-devel/gcc-4.8.4/work/build/./gcc -nostdinc++ -L/var/tmp/portage/sys-devel/gcc-4.8.4/work/build/hppa1.1-unknown-linux-gnu/libstdc++-v3/src -L/var/tmp/portage/sys-devel/gcc-4.8.4/work/build/hppa1.1-unknown-linux-gnu/libstdc++-v3/src/.libs -B/usr/hppa1.1-unknown-linux-gnu/bin/ -B/usr/hppa1.1-unknown-linux-gnu/lib/ -isystem /usr/hppa1.1-unknown-linux-gnu/include -isystem /usr/hppa1.1-unknown-linux-gnu/sys-include    -Wl,-O1 -Wl,-z,relro -Wl,--gc-sections  -prefer-pic -D_GLIBCXX_SHARED  -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi  -fdiagnostics-show-location=once    -ffunction-sections -fdata-sections  -frandom-seed=libsupc++convenience.la  -o libsupc++convenience.la  array_type_info.lo atexit_arm.lo atexit_thread.lo bad_alloc.lo bad_cast.lo bad_typeid.lo class_type_info.lo del_op.lo del_opnt.lo del_opv.lo del_opvnt.lo dynca
 st.lo eh_alloc.lo eh_arm.lo eh_aux_runtime.lo eh_call.lo eh_catch.lo eh_exception.lo eh_globals.lo eh_personality.lo eh_ptr.lo eh_term_handler.lo eh_terminate.lo eh_tm.lo eh_throw.lo eh_type.lo eh_unex_handler.lo enum_type_info.lo function_type_info.lo fundamental_type_info.lo guard.lo guard_error.lo hash_bytes.lo nested_exception.lo new_handler.lo new_op.lo new_opnt.lo new_opv.lo new_opvnt.lo pbase_type_info.lo pmem_type_info.lo pointer_type_info.lo pure.lo si_class_type_info.lo tinfo.lo tinfo2.lo vec.lo vmi_class_type_info.lo vterminate.lo cp-demangle.lo  
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/bin/bash: ../libtool: No such file or directory
Makefile:577: recipe for target 'libsupc++convenience.la' failed
make[5]: *** [libsupc++convenience.la] Error 127
make[5]: Leaving directory '/var/tmp/portage/sys-devel/gcc-4.8.4/work/build/hppa1.1-unknown-linux-gnu/libstdc++-v3/libsupc++'
Makefile:480: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-4.8.4/work/build/hppa1.1-unknown-linux-gnu/libstdc++-v3'
Makefile:386: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-4.8.4/work/build/hppa1.1-unknown-linux-gnu/libstdc++-v3'
Makefile:12221: recipe for target 'all-stage2-target-libstdc++-v3' failed
make[2]: *** [all-stage2-target-libstdc++-v3] Error 2
make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-4.8.4/work/build'
Makefile:17392: recipe for target 'stage2-bubble' failed
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-4.8.4/work/build'
Makefile:17598: recipe for target 'bootstrap-lean' failed
make: *** [bootstrap-lean] Error 2
 * ERROR: sys-devel/gcc-4.8.4::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.8.4::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.8.4::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.8.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.8.4/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.8.4/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4'
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
ebuild-ipc: daemon process not detected
 * 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.
ebuild-ipc: daemon process not detected
 * The ebuild phase 'die_hooks' 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.

 * Messages for package sys-libs/timezone-data-2015b:

 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.

 * 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/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:

 * 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.
 * ERROR: sys-devel/gcc-4.8.4::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.8.4::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.8.4::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.8.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.8.4/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.8.4/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4'

!!! 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-20150724/.catalyst_lock'



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