[gentoo-releng-autobuilds] [s390x-auto] Catalyst fatal build error - stage3.spec

[root]

make[5]: *** [Makefile:641: all-recursive] Error 1
make[5]: Leaving directory '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/build/s390x-ibm-linux-gnu/libstdc++-v3/src'
make[4]: *** [Makefile:510: all-recursive] Error 1
make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/build/s390x-ibm-linux-gnu/libstdc++-v3'
make[3]: *** [Makefile:417: all] Error 2
make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/build/s390x-ibm-linux-gnu/libstdc++-v3'
make[2]: *** [Makefile:14349: all-stage1-target-libstdc++-v3] Error 2
make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/build'
make[1]: *** [Makefile:20902: stage1-bubble] Error 2
make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/build'
make: *** [Makefile:21234: bootstrap-lean] Error 2
 * ERROR: sys-devel/gcc-7.3.0-r3::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-7.3.0-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-7.3.0-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/gcc-7.3.0'
Traceback (most recent call last):
  File "/var/tmp/portage/._portage_reinstall_.dmbi48ff/bin/ebuild-ipc.py", line 277, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/var/tmp/portage/._portage_reinstall_.dmbi48ff/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/var/tmp/portage/._portage_reinstall_.dmbi48ff/bin/ebuild-ipc.py", line 130, in communicate
    lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
  File "/var/tmp/portage/._portage_reinstall_.dmbi48ff/pym/portage/locks.py", line 194, in lockfile
    locking_method = portage._eintr_func_wrapper(_get_lock_fn())
  File "/var/tmp/portage/._portage_reinstall_.dmbi48ff/pym/portage/locks.py", line 62, in _get_lock_fn
    fd, lock_path = tempfile.mkstemp()
  File "/usr/lib64/python3.6/tempfile.py", line 335, in mkstemp
    prefix, suffix, dir, output_type = _sanitize_params(prefix, suffix, dir)
  File "/usr/lib64/python3.6/tempfile.py", line 130, in _sanitize_params
    dir = gettempdir()
  File "/usr/lib64/python3.6/tempfile.py", line 296, in gettempdir
    tempdir = _get_default_tempdir()
  File "/usr/lib64/python3.6/tempfile.py", line 231, in _get_default_tempdir
    dirlist)
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/var/tmp/portage/sys-devel/gcc-7.3.0-r3/temp', '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/temp', '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/temp', '/tmp', '/var/tmp', '/usr/tmp', '/var/tmp/portage/._portage_reinstall_.dmbi48ff/pym']
 * 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.
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/gcc-build-logs.tar.bz2 in your bug report.
 * 
 * Messages for package sys-fs/eudev-3.2.5:
 * 
 * As of 2013-01-29, eudev-3.2.5 provides the new interface renaming functionality,
 * as described in the URL below:
 * https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
 * 
 * This functionality is enabled BY DEFAULT because eudev has no means of synchronizing
 * between the default or user-modified choice of sys-fs/udev.  If you wish to disable
 * this new iface naming, please be sure that /etc/udev/rules.d/80-net-name-slot.rules
 * exists: touch /etc/udev/rules.d/80-net-name-slot.rules
 * 
 * Messages for package sys-apps/opentmpfiles-0.1.3:
 * Auto-adding 'opentmpfiles-dev' service to your sysinit runlevel
 * Auto-adding 'opentmpfiles-setup' service to your boot runlevel
 * Messages for package sys-apps/baselayout-2.4.1-r2:
 * The following users have non-existent shells!
 * halt - /sbin/halt
 * shutdown - /sbin/shutdown
 * You should reboot now to get /run mounted with tmpfs!
 * Messages for package sys-libs/timezone-data-2018e:
 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.
 * Messages for package sys-apps/sysvinit-2.88-r9:
 * 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 net-mail/mailbase-1.1:
 * Your /var/spool/mail/ directory permissions differ from
 *   those which mailbase wants to set it to (03775).
 *   If you did not change them on purpose, consider running:
 * 
 *     chown root:mail /var/spool/mail/
 *     chmod 03775 /var/spool/mail/
 * Messages for package sys-libs/pam-1.2.1-r2:
 * 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.29.0:
 * Could not locate user configfile, so we will save a default one
 * Your configuration for sys-apps/busybox-1.29.0 has been saved in 
 * /etc/portage/savedconfig/sys-apps/busybox-1.29.0 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-apps/util-linux-2.32-r4:
 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
 * The agetty util now clears the terminal by default. You
 * might want to add --noclear to your /etc/inittab lines.
 * Messages for package sys-libs/glibc-2.26-r7:
 * Applying Gentoo Glibc Patchset 2.26-7
 * Generating all locales; edit /etc/locale.gen to save time/space
 * Messages for package sys-apps/coreutils-8.29-r1:
 * 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-devel/gcc-7.3.0-r3:
 * 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-7.3.0-r3::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-7.3.0-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-7.3.0-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/gcc-7.3.0'
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/gcc-build-logs.tar.bz2 in your bug report.
 * 

























!!! 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/lib64/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/lib64/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 stage3
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage3-s390x-20181001T091141Z/.catalyst_lock'
Command exited with non-zero status 1
5006.09user 1394.32system 1:20:13elapsed 132%CPU (0avgtext+0avgdata 2594864maxresident)k
0inputs+0outputs (1931major+764577944minor)pagefaults 0swaps



Full build log at /tmp/catalyst-auto.20181001T091141Z.OtQcCx/log/stage3.log