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

* 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 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/cryptsetup-1.6.2:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Please see the example for configuring a LUKS mountpoint
 * in /etc/conf.d/dmcrypt
 * 
 * If you are using baselayout-2 then please do:
 * rc-update add dmcrypt boot
 * This version introduces a command line arguement 'key_timeout'.
 * If you want the search for the removable key device to timeout
 * after 10 seconds add the following to your bootloader config:
 * key_timeout=10
 * A timeout of 0 will mean it will wait indefinitely.
 * 
 * Users using cryptsetup-1.0.x (dm-crypt plain) volumes must use
 * a compatibility mode when using cryptsetup-1.1.x. This can be
 * done by specifying the cipher (-c), key size (-s) and hash (-h).
 * For more info, see http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup
 * Messages for package sys-fs/dmraid-1.0.0_rc16-r3:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * For booting Gentoo from Device-Mapper RAID you can use a Genkernel initramfs.
 * 
 * Genkernel will generate the kernel and the initramfs with a statically 
 * linked dmraid binary (its own version which may not be the same as this version):
 * 	 emerge -av sys-kernel/genkernel
 * 	 genkernel --dmraid all
 * 
 * A pre-patched distfile of this version of DMRAID has been installed at
 * /usr/share/dmraid/dmraid-1.0.0.rc16-3-prepatched.tar.bz2 , to support using it within a
 * Genkernel initramfs.
 * 
 * If you would rather use this version of DMRAID with Genkernel, update the following
 * in /etc/genkernel.conf:
 * 	 DMRAID_VER="1.0.0.rc16-3"
 * 	 DMRAID_SRCTAR="/usr/share/dmraid/dmraid-1.0.0.rc16-3-prepatched.tar.bz2"
 * 
 * Messages for package sys-fs/multipath-tools-0.5.0-r1:
 * If you need multipath on your system, you must
 * add 'multipath' into your boot runlevel!
 * Messages for package app-misc/livecd-tools-2.0.3:
 * 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!!!
 * Messages for package sys-libs/glibc-2.17:
 * Defaulting /etc/host.conf:multi to on
 * Generating all locales; edit /etc/locale.gen to save time/space
 * Messages for package sys-apps/openrc-0.12.4:
 * 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
 * This version of OpenRC doesn't enable nfs mounts automatically any
 * longer. In order to mount nfs file systems, you must use the
 * nfsmount service from the nfs-utils package.
 * See bug https://bugs.gentoo.org/show_bug.cgi?id=427996 for
 * more information on this.
 * 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.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 3847:  Called toolchain_src_compile
 *   environment, line 4567:  Called gcc_do_make
 *   environment, line 2009:  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 1402, in build_packages
    "Error in attempt to build packages",env=self.env)
  File "/usr/lib64/catalyst//modules/catalyst_support.py", line 539, 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 1303, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1407, 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-20140410/.catalyst_lock'



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