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

>>> Installing (131 of 207) sys-apps/shadow-4.6::gentoo
>>> Installing (132 of 207) dev-python/setuptools-40.6.3::gentoo
>>> Emerging binary (133 of 207) virtual/shadow-0::gentoo
>>> Installing (133 of 207) virtual/shadow-0::gentoo
>>> Emerging binary (134 of 207) net-misc/openssh-8.0_p1-r4::gentoo
>>> Installing (134 of 207) net-misc/openssh-8.0_p1-r4::gentoo
>>> Emerging binary (135 of 207) virtual/ssh-0::gentoo
>>> Installing (135 of 207) virtual/ssh-0::gentoo
>>> Emerging (136 of 207) dev-python/pyblake2-1.1.2::gentoo
>>> Installing (136 of 207) dev-python/pyblake2-1.1.2::gentoo
>>> Emerging (137 of 207) dev-python/pyxattr-0.6.0-r1::gentoo
>>> Installing (137 of 207) dev-python/pyxattr-0.6.0-r1::gentoo
>>> Emerging (138 of 207) dev-python/certifi-2019.6.16::gentoo
>>> Installing (138 of 207) dev-python/certifi-2019.6.16::gentoo
>>> Emerging (139 of 207) dev-python/bz2file-0.98::gentoo
>>> Installing (139 of 207) dev-python/bz2file-0.98::gentoo
>>> Emerging (140 of 207) app-portage/gemato-14.3::gentoo
>>> Installing (140 of 207) app-portage/gemato-14.3::gentoo
>>> Emerging binary (141 of 207) sys-apps/portage-2.3.79::gentoo
>>> Installing (141 of 207) sys-apps/portage-2.3.79::gentoo
>>> Emerging binary (142 of 207) virtual/package-manager-1::gentoo
>>> Installing (142 of 207) virtual/package-manager-1::gentoo
>>> Emerging binary (143 of 207) sys-apps/openrc-0.41.2::gentoo
>>> Installing (143 of 207) sys-apps/openrc-0.41.2::gentoo
>>> Emerging binary (144 of 207) net-misc/netifrc-0.5.1::gentoo
>>> Installing (144 of 207) net-misc/netifrc-0.5.1::gentoo
>>> Emerging binary (145 of 207) virtual/service-manager-0::gentoo
>>> Installing (145 of 207) virtual/service-manager-0::gentoo
>>> Emerging binary (146 of 207) sys-fs/eudev-3.2.9::gentoo
>>> Installing (146 of 207) sys-fs/eudev-3.2.9::gentoo
>>> Emerging binary (147 of 207) virtual/udev-217::gentoo
>>> Installing (147 of 207) virtual/udev-217::gentoo
>>> Emerging binary (148 of 207) sys-fs/udev-init-scripts-33::gentoo
>>> Installing (148 of 207) sys-fs/udev-init-scripts-33::gentoo
>>> Emerging binary (149 of 207) sys-apps/hwids-20190818::gentoo
>>> Installing (149 of 207) sys-apps/hwids-20190818::gentoo
>>> Emerging binary (150 of 207) virtual/dev-manager-0-r2::gentoo
>>> Installing (150 of 207) virtual/dev-manager-0-r2::gentoo
>>> Emerging (151 of 207) dev-lang/perl-5.30.1::gentoo
>>> Failed to emerge dev-lang/perl-5.30.1
 * Messages for package sys-apps/portage-2.3.79:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Messages for package sys-fs/eudev-3.2.9:
 * 
 * As of 2013-01-29, eudev-3.2.9 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.2:
 * 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.6-r1:
 * 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-2019c:
 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.
 * Messages for package sys-apps/sysvinit-2.93:
 * 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.30:
 * 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/glibc-2.29-r2:
 * Generating all locales; edit /etc/locale.gen to save time/space
 * Messages for package sys-devel/gcc-9.2.0-r2:
 * 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):
 * https://wiki.gentoo.org/wiki/Upgrading_GCC
 * Messages for package app-crypt/gnupg-2.2.17:
 * See https://wiki.gentoo.org/wiki/GnuPG for documentation on gnupg
 * 
 * If you wish to use 'gpg-wks-client --send', you must install an MTA!
 * Messages for package sys-apps/man-db-2.7.6.1-r2:
 * Defaulting to USE=gdbm due to ambiguous berkdb/gdbm USE flag settings
 * Messages for package sys-libs/pam-1.3.0-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/util-linux-2.33.2:
 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
 * Messages for package net-misc/netifrc-0.5.1:
 * The network configuration scripts will use dhcp by
 * default to set up your interfaces.
 * If you need to set up something more complete, see
 * //usr/share/doc/netifrc-0.5.1/README
 * Messages for package sys-fs/eudev-3.2.9:
 * 
 * For more information on eudev on Gentoo, writing udev rules, and
 * fixing known issues visit: https://wiki.gentoo.org/wiki/Eudev
 * Messages for package sys-fs/udev-init-scripts-33:
 * Adding udev to the sysinit runlevel
 * Adding udev-trigger to the sysinit runlevel
 * Messages for package dev-lang/perl-5.30.1:
 * The ebuild phase 'unpack' 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.


































09 Dec 2019 01:58:14 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1
ERROR:catalyst:CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1
09 Dec 2019 01:58:14 UTC: ERROR   : CatalystError: Stage build aborting due to error.
ERROR:catalyst:CatalystError: Stage build aborting due to error.
09 Dec 2019 01:58:14 UTC: ERROR   : Exception running action sequence run_local
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1360, in run_local
    env=self.env)
  File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
    print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1465, in run
    getattr(self, x)()
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1369, in run_local
    print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
ERROR:catalyst:Exception running action sequence run_local
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1360, in run_local
    env=self.env)
  File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
    print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1465, in run
    getattr(self, x)()
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1369, in run_local
    print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
09 Dec 2019 01:58:14 UTC: NOTICE  : Cleaning up... Running unbind()
NOTICE:catalyst:Cleaning up... Running unbind()
Command exited with non-zero status 2
1751.01user 283.97system 24:09.28elapsed 140%CPU (0avgtext+0avgdata 206484maxresident)k
490880inputs+6902832outputs (3major+51715717minor)pagefaults 0swaps



Full build log at /release/tmp/run/catalyst-auto.20191208T214503Z.EFONUd/log/stage3-x32.log