Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@××××××××××××××××××××.org
To: releng@g.o, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [hppa-auto] Catalyst fatal build error - hppa1.1/stage1.spec
Date: Mon, 17 Sep 2018 17:43:07
Message-Id: 20180917174306.68065E09BF@pigeon.gentoo.org
*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f hppa1.1/stage1.spec
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/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to config file value "/usr/local/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/usr/local/catalyst"
Setting portdir to config file value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "autoresume bindist pkgcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: stage1
Building natively for hppa
stage1 root path is /tmp/stage1root
Source path set to /usr/local/catalyst/builds/default/stage3-hppa1.1-latest.tar.bz2
Caching snapshot to /usr/local/catalyst/snapshot_cache/20180917T165732Z/
The autoresume path is /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa1.1-20180917T165732Z/
stage1 stage path is /usr/local/catalyst/tmp/default/stage1-hppa1.1-20180917T165732Z/tmp/stage1root
Location of the package cache is /var/tmp/catalyst/packages/default/stage1-hppa1.1
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa1.1-20180917T165732Z/
--- Running action sequence: unpack
No Valid Resume point detected, cleaning up...
Removing AutoResume Points: ...
Emptying directory /usr/local/catalyst/tmp/default/.autoresume-stage1-hppa1.1-20180917T165732Z/
Emptying directory /usr/local/catalyst/tmp/default/stage1-hppa1.1-20180917T165732Z/

Starting tar extract from /usr/local/catalyst/builds/default/stage3-hppa1.1-latest.tar.bz2
to /usr/local/catalyst/tmp/default/stage1-hppa1.1-20180917T165732Z/ (This may take some time) ...

tar: SELinux support is not available
--- Running action sequence: unpack_snapshot
Cleaning up invalid snapshot cache at 
	/usr/local/catalyst/snapshot_cache/20180917T165732Z/ (This can take a long time)...
Unpacking portage tree (This can take a long time) ...
tar: SELinux support is not available
lockfile does not exist '/usr/local/catalyst/snapshot_cache/20180917T165732Z/.catalyst_lock'
--- Running action sequence: setup_confdir
Configuring /etc/portage...
--- 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 /usr/local/catalyst/tmp/default/stage1-hppa1.1-20180917T165732Z///tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /usr/local/catalyst/tmp/default/stage1-hppa1.1-20180917T165732Z//tmp
copying chroot-functions.sh to /usr/local/catalyst/tmp/default/stage1-hppa1.1-20180917T165732Z//tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot /usr/local/catalyst/tmp/default/stage1-hppa1.1-20180917T165732Z/
>>> 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.) !!! The following installed packages are masked: - sys-libs/glibc-2.25-r11::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Michał Górny <mgorny@g.o>, Andreas K. Hüttel <dilfridge@g.o>, # Matthias Maier <tamiko@g.o> (21 May 2017 and later updates) # These old versions of toolchain packages (binutils, gcc, glibc) are no # longer officially supported and are not suitable for general use. Using # these packages can result in build failures (and possible breakage) for # many packages, and may leave your system vulnerable to known security # exploits. # If you still use one of these old toolchain packages, please upgrade (and # switch the compiler / the binutils) ASAP. If you need them for a specific # (isolated) use case, feel free to unmask them on your system. - net-libs/libnsl-0-r1::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Andreas K. Hüttel <dilfridge@g.o> (11 Sep 2018) # Mask transition ebuilds that were needed only for <glibc-2.26 # We will keep them in the tree as long as we have masked # <glibc-2.26. For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.
>>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-apps/portage-2.3.40-r1::gentoo >>> Installing (1 of 1) sys-apps/portage-2.3.40-r1::gentoo
Updating seed stage... emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc The following packages are causing rebuilds: (net-firewall/iptables-1.6.1-r3:0/12::gentoo, ebuild scheduled for merge) causes rebuilds for: (sys-apps/iproute2-4.14.1-r2:0/0::gentoo, ebuild scheduled for merge) !!! The following installed packages are masked: - net-libs/libnsl-0-r1::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Andreas K. Hüttel <dilfridge@g.o> (11 Sep 2018) # Mask transition ebuilds that were needed only for <glibc-2.26 # We will keep them in the tree as long as we have masked # <glibc-2.26. - sys-libs/glibc-2.25-r11::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Michał Górny <mgorny@g.o>, Andreas K. Hüttel <dilfridge@g.o>, # Matthias Maier <tamiko@g.o> (21 May 2017 and later updates) # These old versions of toolchain packages (binutils, gcc, glibc) are no # longer officially supported and are not suitable for general use. Using # these packages can result in build failures (and possible breakage) for # many packages, and may leave your system vulnerable to known security # exploits. # If you still use one of these old toolchain packages, please upgrade (and # switch the compiler / the binutils) ASAP. If you need them for a specific # (isolated) use case, feel free to unmask them on your system. For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.
>>> Verifying ebuild manifests >>> Running pre-merge checks for sys-devel/gcc-7.3.0-r3 >>> Running pre-merge checks for net-misc/openssh-7.7_p1-r9 >>> Emerging (1 of 31) app-arch/bzip2-1.0.6-r10::gentoo >>> Installing (1 of 31) app-arch/bzip2-1.0.6-r10::gentoo
/proc is still mounted; performing auto-bind-umount... Auto-unbind successful... Traceback (most recent call last): File "/usr/lib/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 1244, in run_local "run script failed.",env=self.env) File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, in cmd retval=spawn_bash(mycmd,env) File "/usr/lib/catalyst/modules/catalyst_support.py", line 306, in spawn_bash return spawn(args,env=env,opt_name=opt_name,**keywords) File "/usr/lib/catalyst/modules/catalyst_support.py", line 523, in spawn retval=os.waitpid(mypid[-1],0)[1] KeyboardInterrupt !!! catalyst: Error encountered during run of target stage1 Catalyst aborting.... lockfile does not exist '/usr/local/catalyst/tmp/default/stage1-hppa1.1-20180917T165732Z/.catalyst_lock' Command exited with non-zero status 1 334.21user 74.35system 24:18.53elapsed 28%CPU (0avgtext+0avgdata 14616maxresident)k 0inputs+0outputs (16major+1052226minor)pagefaults 0swaps Full build log at /tmp/catalyst-auto.20180917T165732Z.nJRKcn/log/hppa1.1_stage1.log