[gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - installcd-stage1.spec

* 
 * please be sure /etc/brltty.conf is correct for your system.
 * 
 * To make brltty start on boot, type this command as root:
 * 
 * rc-update add brltty boot
 * Messages for package app-admin/hddtemp-0.3_beta15-r7:
 * In order to update your hddtemp database, run:
 * emerge --config =app-admin/hddtemp-0.3_beta15-r7
 * 
 * If your hard drive is not recognized by hddtemp, please consider
 * submitting your HDD info for inclusion into the Gentoo hddtemp
 * database by filing a bug at https://bugs.gentoo.org/
 * 
 * If hddtemp complains but finds your HDD temperature sensor, use the
 * --quiet option to suppress the warning.
 * 
 * (Note: Above message is only printed the first time package is
 * installed. Please look at /usr/share/doc/hddtemp-0.3_beta15-r7/README.gentoo*
 * for future reference)
 * Messages for package sys-power/acpid-2.0.20:
 * 
 * You may wish to read the Gentoo Linux Power Management Guide,
 * which can be found online at:
 * http://www.gentoo.org/doc/en/power-management-guide.xml
 * 
 * Messages for package net-misc/ntp-4.2.6_p5-r10:
 * You can find an example /etc/ntp.conf in /usr/share/ntp/
 * Review /etc/ntp.conf to setup server info.
 * Review /etc/conf.d/ntpd to setup init.d info.
 * The way ntp sets and maintains your system time has changed.
 * Now you can use /etc/init.d/ntp-client to set your time at
 * boot while you can use /etc/init.d/ntpd to maintain your time
 * while your machine runs
 * Messages for package net-misc/dhcpcd-6.4.3:
 * 
 * dhcpcd has zeroconf support active by default.
 * This means it will always obtain an IP address even if no
 * DHCP server can be contacted, which will break any existing
 * failover support you may have configured in your net configuration.
 * This behaviour can be controlled with the noipv4ll configuration
 * file option or the -L command line switch.
 * See the dhcpcd and dhcpcd.conf man pages for more details.
 * 
 * Dhcpcd has duid enabled by default, and this may cause issues
 * with some dhcp servers. For more information, see
 * https://bugs.gentoo.org/show_bug.cgi?id=477356
 * 
 * If you activate the lookup-hostname hook to look up your hostname
 * using the dns, you need to install net-dns/bind-tools.
 * Messages for package net-wireless/wpa_supplicant-2.0-r2:
 * If this is a clean installation of wpa_supplicant, you
 * have to create a configuration file named
 * /etc/wpa_supplicant/wpa_supplicant.conf
 * 
 * An example configuration file is available for reference in
 * /usr/share/doc/wpa_supplicant-2.0-r2/
 * Messages for package sys-apps/util-linux-2.24.1-r3:
 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
 * Messages for package sys-fs/mdadm-3.2.6-r1:
 * If you're not relying on kernel auto-detect of your RAID
 * devices, you need to add 'mdraid' to your 'boot' runlevel:
 * 	rc-update add mdraid boot
 * Messages for package sys-libs/libkudzu-1.2.57.1:
 * QA: Kernel version could not be determined, please inherit kernel-2 or linux-info
 * Messages for package sys-apps/hwsetup-1.2-r2:
 * This package is designed for use on the LiveCD only and will do 
 * unspeakably horrible and unexpected things on a normal system.
 * YOU HAVE BEEN WARNED!!!
 * This package is intended for usage on the Gentoo release media.  If
 * you are not building a CD, remove this package.  It will not work
 * properly on a running system, as Gentoo does not use any of the
 * Knoppix-style detection except for CD builds.
 * Messages for package sys-fs/udev-215-r1:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * 
 * Starting from version >= 197 the new predictable network interface names are
 * used by default, see:
 * http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
 * http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c
 * 
 * Example command to get the information for the new interface name before booting
 * (replace <ifname> with, for example, eth0):
 * # udevadm test-builtin net_id /sys/class/net/<ifname> 2> /dev/null
 * 
 * You can use either kernel parameter "net.ifnames=0", create empty
 * file /etc/systemd/network/99-default.link, or symlink it to /dev/null
 * to disable the feature.
 * 
 * You need to restart udev as soon as possible to make the upgrade go
 * into effect.
 * The method you use to do this depends on your init system.
 * For sys-apps/openrc users it is:
 * # /etc/init.d/udev --nodeps restart
 * 
 * For more information on udev on Gentoo, upgrading, writing udev rules, and
 * fixing known issues visit:
 * http://wiki.gentoo.org/wiki/Udev
 * http://wiki.gentoo.org/wiki/Udev/upgrade
 * Messages for package sys-fs/e2fsprogs-1.42.10:
 * No /etc/mtab file, creating one temporarily
 * Messages for package sys-devel/gcc-4.7.3-r1:
 * ERROR: sys-devel/gcc-4.7.3-r1::gentoo failed (compile phase):
 *   emake failed with bootstrap-lean
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 3780:  Called toolchain_src_compile
 *   environment, line 4499:  Called gcc_do_make
 *   environment, line 1949:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.7.3-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.7.3-r1::gentoo'`.
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-build-logs.tar.bz2 in your bug report.
 * 
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3'



















































!!! existing preserved libs found

!!! catalyst: Error in attempt to build packages


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1403, in build_packages
    "Error in attempt to build packages",env=self.env)
  File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: livecdbuild 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 1408, in build_packages
    "build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target livecd-stage1
Catalyst aborting....
lockfile does not exist '/release/buildroot/amd64-dev/tmp/default/livecd-stage1-amd64-20140731/.catalyst_lock'



Full build log at /release/tmp/run/catalyst-auto.22415/log/installcd-stage1.log