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

* 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 use 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-216:

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

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Make sure the "lvm" init script is in the runlevels:
 * # rc-update add lvm boot
 * 
 * Make sure to enable lvmetad in /etc/lvm/lvm.conf if you want
 * to enable lvm autoactivation and metadata caching.

 * Messages for package app-portage/mirrorselect-2.2.2:

 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.

 * Messages for package sys-fs/ntfs3g-2013.1.13:

 * 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 app-crypt/gnupg-2.0.26:

 * If you wish to view images emerge:
 * media-gfx/xloadimage, media-gfx/xli or any other viewer
 * Remember to use photo-viewer option in configuration file to activate
 * the right viewer.
 * 
 * Please remember to restart gpg-agent if a different version
 * of the agent is currently used. If you are unsure of the gpg
 * agent you are using please run 'killall gpg-agent',
 * and to start a fresh daemon just run 'gpg-agent --daemon'.

 * Messages for package sys-fs/cryptsetup-1.6.5:

 * 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 dev-libs/glib-2.40.0-r1:

 * 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-apps/dbus-1.8.8:

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * To start the D-Bus system-wide messagebus by default
 * you should add it to the default runlevel :
 * `rc-update add dbus default`
 * 
 * Some applications require a session bus in addition to the system
 * bus. Please see `man dbus-launch` for more information.
 * 

 * Messages for package app-admin/syslog-ng-3.4.8:

 * For detailed documentation please see the upstream website:
 * http://www.balabit.com/sites/default/files/documents/syslog-ng-ose-3.4-guides/en/syslog-ng-ose-v3.4-guide-admin/html/index.html
 * It is highly recommended that app-admin/logrotate be emerged to
 * manage the log files.  syslog-ng installs a file in /etc/logrotate.d
 * for logrotate to use.

 * Messages for package app-misc/livecd-tools-2.0.4:

 * 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.19-r1:

 * Defaulting /etc/host.conf:multi to on
 * ERROR: sys-libs/glibc-2.19-r1::gentoo failed (preinst phase):
 *   simple run test (/usr/bin/cal) failed
 * 
 * Call stack:
 *           ebuild.sh, line   93:  Called pkg_preinst
 *         environment, line 2910:  Called eblit-run 'pkg_preinst'
 *         environment, line 1029:  Called eblit-glibc-pkg_preinst
 *   pkg_preinst.eblit, line   54:  Called glibc_sanity_check
 *   pkg_preinst.eblit, line   33:  Called die
 * The specific snippet of code:
 *   		./ld-*.so --library-path . ${x} > /dev/null \
 *   			|| die "simple run test (${x}) failed"
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.19-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.19-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/glibc-2.19-r1/image/lib64'
 * S: '/var/tmp/portage/sys-libs/glibc-2.19-r1/work/glibc-2.19'

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



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