From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 99FA3138A1A for ; Thu, 22 Jan 2015 01:16:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7DF54E084F; Thu, 22 Jan 2015 01:16:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1D4ADE084F for ; Thu, 22 Jan 2015 01:16:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id DDC6F3406F0 for ; Thu, 22 Jan 2015 01:16:27 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -0.307 X-Spam-Level: X-Spam-Status: No, score=-0.307 tagged_above=-999 required=5.5 tests=[AWL=-0.297, T_RP_MATCHES_RCVD=-0.01] autolearn=no Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AT5dt0ZxaZDp for ; Thu, 22 Jan 2015 01:16:21 +0000 (UTC) Received: from nightheron.gentoo.org (nightheron.gentoo.org [154.52.129.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 78168340707 for ; Thu, 22 Jan 2015 01:16:21 +0000 (UTC) Received: by nightheron.gentoo.org (Postfix, from userid 0) id 56EFE2AF9D; Thu, 22 Jan 2015 01:16:19 +0000 (UTC) From: catalyst@nightheron.gentoo.org To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage1.spec Message-Id: <20150122011619.56EFE2AF9D@nightheron.gentoo.org> Date: Thu, 22 Jan 2015 01:16:19 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Release Engineering Autobuilds X-BeenThere: gentoo-releng-autobuilds@gentoo.org X-BeenThere: gentoo-releng-autobuilds@lists.gentoo.org Reply-To: gentoo-releng-autobuilds@lists.gentoo.org X-Archives-Salt: fdb55fca-129b-48d0-94b5-de8eb2e2dabb X-Archives-Hash: 9e9c34aac1815b2a4591027f7f3e3124 Catalyst, version 2.0.18 Copyright 2003-2008 Gentoo Foundation Copyright 2008-2012 various authors Distributed under the GNU General Public License version 2.1 Using command line specified Catalyst configuration file, /etc/catalyst/release/amd64-auto.conf Setting sharedir to config file value "/usr/lib64/catalyst/" Setting snapshot_cache to config file value "/release/tmp/snapshots" Setting hash_function to config file value "crc32" Setting storedir to config file value "/release/buildroot/amd64-dev" Setting portdir to config file value "/release/trees/portage-auto" Setting distdir to config file value "/usr/portage/distfiles" Setting options to config file value "autoresume bindist pkgcache preserve_libs seedcache snapcache" Autoresuming support enabled. Binary redistribution enabled Package cache support enabled. Preserving libs during unmerge. Seed cache support enabled. Snapshot cache support enabled. Envscript support enabled. Using target: stage1 Building natively for amd64 stage1 root path is /tmp/stage1root Source path set to /release/buildroot/amd64-dev/builds/default/stage3-amd64-latest.tar.bz2 Caching snapshot to /release/tmp/snapshots/20150122/ The autoresume path is /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-amd64-20150122/ stage1 stage path is /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122/tmp/stage1root Location of the package cache is /release/buildroot/amd64-dev/packages/default/stage1-amd64-20150122/ Checking for processes running in chroot and killing them. Removing AutoResume Points: ... Emptying directory /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-amd64-20150122/ >>> Waiting 10 seconds before starting... >>> (Control-C to abort)... Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 clearing autoresume ... Removing AutoResume Points: ... Emptying directory /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-amd64-20150122/ clearing chroot ... Emptying directory /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122/ clearing package cache ... purging the pkgcache ... clearing kerncache ... --- Running action sequence: unpack Referenced SEEDCACHE does not appear to be a directory, trying to untar... No Valid Resume point detected, cleaning up... Removing AutoResume Points: ... Emptying directory /release/buildroot/amd64-dev/tmp/default/.autoresume-stage1-amd64-20150122/ Emptying directory /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122/ Starting tar extract from /release/buildroot/amd64-dev/builds/default/stage3-amd64-latest.tar.bz2 to /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122/ (This may take some time) ... tar: XATTR support is not available tar: SELinux support is not available --- Running action sequence: unpack_snapshot Cleaning up invalid snapshot cache at /release/tmp/snapshots/20150122/ (This can take a long time)... Unpacking portage tree (This can take a long time) ... tar: XATTR support is not available tar: SELinux support is not available lockfile does not exist '/release/tmp/snapshots/20150122/.catalyst_lock' --- Running action sequence: setup_confdir --- Running action sequence: portage_overlay --- Running action sequence: base_dirs --- Running action sequence: bind --- Running action sequence: chroot_setup Setting up chroot... Warning!!!! Overriding certain env variables may cause catastrophic failure. If your build fails look here first as the possible problem. Catalyst assumes you know what you are doing when setting these variables. Catalyst Maintainers use VERY minimal envscripts if used at all You have been warned --- Running action sequence: setup_environment --- Running action sequence: run_local copying make.conf to /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122///tmp/stage1root/etc/portage Copying stage1-chroot.sh to /tmp copying stage1-chroot.sh to /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122//tmp copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122//tmp Ensure the file has the executable bit set Running stage1-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122/ >>> Regenerating /etc/ld.so.cache... Adding USE=' build' to make.conf for portage build emerge --quiet --oneshot --update --newuse sys-apps/portage Performing Global Updates (Could take a couple of minutes if you have a lot of binary packages.) >>> Verifying ebuild manifests >>> Emerging (1 of 2) dev-lang/python-exec-2.0.1-r1 >>> Failed to emerge dev-lang/python-exec-2.0.1-r1, Log file: >>> '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/temp/build.log' * Package: dev-lang/python-exec-2.0.1-r1 * Repository: gentoo * Maintainer: python@gentoo.org * Upstream: mgorny@gentoo.org https://bitbucket.org/mgorny/python-exec/issues/ * USE: abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_jython2_5 python_targets_jython2_7 python_targets_pypy python_targets_pypy3 python_targets_python2_7 python_targets_python3_3 python_targets_python3_4 userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Running elibtoolize in: python-exec-2.0.1/ >>> Working in BUILD_DIR: "/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/work/python-exec-2.0.1_build" checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... configure: error: in `/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/work/python-exec-2.0.1_build': configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-lang/python-exec-2.0.1-r1/work/python-exec-2.0.1_build/config.log * ERROR: dev-lang/python-exec-2.0.1-r1::gentoo failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 4090: Called autotools-utils_src_configure * environment, line 933: Called econf '--docdir=/usr/share/doc/python-exec-2.0.1-r1' '--with-eprefix=' '--with-python-impls= jython2.5 jython2.7 pypy pypy3 python3.3 python3.4 python2.7' * phase-helpers.sh, line 584: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of `emerge --info '=dev-lang/python-exec-2.0.1-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-lang/python-exec-2.0.1-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/temp/environment'. * Working directory: '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/work/python-exec-2.0.1_build' * S: '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/work/python-exec-2.0.1' * Messages for package dev-lang/python-exec-2.0.1-r1: * ERROR: dev-lang/python-exec-2.0.1-r1::gentoo failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 4090: Called autotools-utils_src_configure * environment, line 933: Called econf '--docdir=/usr/share/doc/python-exec-2.0.1-r1' '--with-eprefix=' '--with-python-impls= jython2.5 jython2.7 pypy pypy3 python3.3 python3.4 python2.7' * phase-helpers.sh, line 584: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of `emerge --info '=dev-lang/python-exec-2.0.1-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-lang/python-exec-2.0.1-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/temp/environment'. * Working directory: '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/work/python-exec-2.0.1_build' * S: '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/work/python-exec-2.0.1' !!! catalyst: run script failed. Traceback (most recent call last): File "modules/generic_stage_target.py", line 1244, in run_local "run script failed.",env=self.env) File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd raise CatalystError,myexc CatalystError None !!! catalyst: Stage build 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 1249, in run_local raise CatalystError,"Stage build aborting due to error." CatalystError !!! catalyst: Error encountered during run of target stage1 Catalyst aborting.... lockfile does not exist '/release/buildroot/amd64-dev/tmp/default/stage1-amd64-20150122/.catalyst_lock' Full build log at /release/tmp/run/catalyst-auto.Wi8Tar/log/stage1.log