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

[catalyst@lantean.jmbsvicetto.name]

 * Note: chname requires a or later kernel with CONFIG_UTS_NS=y.

 * Messages for package sys-block/tw_cli-10.2:

 * This binary supports should support ALL cards, including, but not
 * limited to the following series:
 * 
 * PATA: 6xxx, 72xx, 74xx, 78xx, 7000, 7500, 7506
 * SATA: 8006, 8500, 8506, 9500S, 9550SX, 9590SE,
 *       9550SXU, 9650SE, 9650SE-{24M8,4LPME},
 *       9690SA, 9750
 * 
 * Release notes for this version are available at:
 * http://www.lsi.com/DistributionSystem/AssetDocument/10.2_Release_Notes_Web.pdf
 * Upstream's 10.2 release is missing the tw_cli manpage.

 * Messages for package net-dialup/ppp-2.4.7:

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Pon, poff and plog scripts have been supplied for experienced users.
 * Users needing particular scripts (ssh,rsh,etc.) should check out the
 * /usr/share/doc/ppp-2.4.7/scripts directory.

 * Messages for package app-emacs/emacs-common-gentoo-1.5:

 * All site initialisation for Gentoo-installed packages is added to
 * /usr/share/emacs/site-lisp/site-gentoo.el. In order for this site
 * initialisation to be loaded for all users automatically, a default
 * site startup file /etc/emacs/site-start.el is installed. You are
 * responsible for maintenance of this file.
 * 
 * Alternatively, individual users can add the following command:
 * 
 * (require 'site-gentoo)
 * 
 * to their ~/.emacs initialisation files, or, for greater flexibility,
 * users may load single package-specific initialisation files from the
 * /usr/share/emacs/site-lisp/site-gentoo.d/ directory.
 * 
 * (Note: Above message is only printed the first time package is
 * installed. Please look at /usr/share/doc/emacs-common-gentoo-1.5/README.gentoo*
 * for future reference)

 * Messages for package sys-apps/openrc-0.17:

 * 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
 * 
 * Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not
 * fixed correctly in earlier versions of OpenRC.
 * The correct fix is implemented in this version, but that
 * means netmount needs to be added to the default runlevel if
 * you are using nfs file systems.
 * 
 * You should now update all files in /etc, using etc-update
 * or equivalent before restarting any services or this host.

 * Messages for package sys-fs/fuse-2.9.4:

 * 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 dev-lang/ocaml-3.12.1:

 * Ocaml generates its own native asm, you're using a PIE compiler
 * We have appended -nopie to ocaml build options
 * because linking an executable with pie while the objects are not pic will not work
 * OCaml is not binary compatible from version to version, so you
 * need to rebuild all packages depending on it, that are actually
 * installed on your system. To do so, you can run:
 * emerge @ocaml-rebuild
 * Or, (almost) equivalently: emerge -1 /usr/lib/ocaml

 * Messages for package dev-python/jinja-2.7.3:

 * For i18n support, please emerge dev-python/Babel.

 * Messages for package app-shells/zsh-5.0.5:

 * If you want to enable Portage completions and Gentoo prompt,
 * emerge app-shells/gentoo-zsh-completions and add
 * 	autoload -U compinit promptinit
 * 	compinit
 * 	promptinit; prompt gentoo
 * to your ~/.zshrc
 * Also, if you want to enable cache for the completions, add
 * 	zstyle ':completion::complete:*' use-cache 1
 * to your ~/.zshrc
 * Note that a system zprofile startup file is installed. This will override
 * PATH and possibly other variables that a user may set in ~/.zshenv.
 * Custom PATH settings and similar overridden variables can be moved to ~/.zprofile
 * or other user startup files that are sourced after the system zprofile.
 * If PATH must be set in ~/.zshenv to affect things like non-login ssh shells,
 * one method is to use a separate path-setting file that is conditionally sourced
 * in ~/.zshenv and also sourced from ~/.zprofile. For more information, see the
 * zshenv example in //usr/share/doc/zsh-5.0.5/StartupFiles/.

 * Messages for package net-wireless/wpa_supplicant-2.4-r3:

 * 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.4-r3/

 * Messages for package sys-apps/x86info-1.30:

 * 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-power/acpid-2.0.23:

 * 
 * 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 sys-process/iotop-0.6:

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 *   CONFIG_TASK_IO_ACCOUNTING:	 is not set when it should be.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.

 * Messages for package dev-util/ctags-5.8:

 * You can set the version to be started by /usr/bin/ctags through
 * the ctags eselect module. "man ctags.eselect" for details.

 * Messages for package net-misc/dhcpcd-6.9.0:

 * 
 * 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 dev-lang/python-3.4.1:

 * You have just upgraded from an older version of Python.
 * 
 * Please adjust PYTHON_TARGETS (if so desired), and run emerge with the --newuse or --changed-use option to rebuild packages installing python modules.

 * Messages for package sys-block/thin-provisioning-tools-0.3.2-r1:

 * ERROR: sys-block/thin-provisioning-tools-0.3.2-r1::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-block/thin-provisioning-tools-0.3.2-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-block/thin-provisioning-tools-0.3.2-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/work/thin-provisioning-tools-0.3.2'
 * S: '/var/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/work/thin-provisioning-tools-0.3.2'

!!! catalyst: Error in attempt to build packages


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1432, 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 1333, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1437, 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-20150722/.catalyst_lock'



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