[gentoo-releng-autobuilds] [x86-auto] Catalyst non-fatal build error - hardened/admincd-stage1.spec

* 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.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 dev-libs/glib-2.38.2-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 app-admin/syslog-ng-3.4.7:
 * 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-emulation/xen-tools-4.2.4-r2:
 * ERROR: app-emulation/xen-tools-4.2.4-r2::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=app-emulation/xen-tools-4.2.4-r2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/xen-tools-4.2.4-r2::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/app-emulation/xen-tools-4.2.4-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/xen-tools-4.2.4-r2/temp/environment'.
 * Working directory: '/var/tmp/portage/app-emulation/xen-tools-4.2.4-r2/work/xen-4.2.4'
 * S: '/var/tmp/portage/app-emulation/xen-tools-4.2.4-r2/work/xen-4.2.4'













































































































!!! 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 '/home/release/buildroot/x86-dev/tmp/hardened/livecd-stage1-x86-20140618/.catalyst_lock'



Full build log at /home/release/tmp/run/catalyst-auto.16457/log/hardened_admincd-stage1.log