Gentoo Archives: gentoo-releng-autobuilds

From: root <vapier@g.o>
To: releng@g.o, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [s390x-auto] Catalyst fatal build error - stage1.spec
Date: Sun, 14 Jan 2018 10:13:10
Message-Id: 20180114101305.7F7F42054E@nightheron.gentoo.org
1 Catalyst, version 2.0.18
2 Copyright 2003-2008 Gentoo Foundation
3 Copyright 2008-2012 various authors
4 Distributed under the GNU General Public License version 2.1
5
6 Using command line specified Catalyst configuration file, /etc/catalyst/catalyst.conf
7 Setting sharedir to config file value "/usr/lib64/catalyst"
8 Setting snapshot_cache to config file value "/var/tmp/catalyst/snapshot_cache"
9 Setting hash_function to config file value "crc32"
10 Setting storedir to config file value "/var/tmp/catalyst"
11 Setting portdir to config file value "/usr/portage"
12 Setting distdir to config file value "/usr/portage/distfiles"
13 Setting options to config file value "autoresume bindist kerncache pkgcache seedcache snapcache"
14 Autoresuming support enabled.
15 Binary redistribution enabled
16 Kernel cache support enabled.
17 Package cache support enabled.
18 Seed cache support enabled.
19 Snapshot cache support enabled.
20 Envscript support enabled.
21 Using target: stage1
22 Building natively for s390
23 stage1 root path is /tmp/stage1root
24 Source path set to /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2
25 Caching snapshot to /var/tmp/catalyst/snapshot_cache/20180114T101027Z/
26 The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390x-20180114T101027Z/
27 stage1 stage path is /var/tmp/catalyst/tmp/default/stage1-s390x-20180114T101027Z/tmp/stage1root
28 Location of the package cache is /var/tmp/catalyst/packages/default/stage1-s390x-20180114T101027Z/
29 Location of the kerncache is /var/tmp/catalyst/kerncache/default/stage1-s390x-20180114T101027Z/
30 Checking for processes running in chroot and killing them.
31 Removing AutoResume Points: ...
32 Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390x-20180114T101027Z/
33 --- Running action sequence: unpack
34 Referenced SEEDCACHE does not appear to be a directory, trying to untar...
35 No Valid Resume point detected, cleaning up...
36 Removing AutoResume Points: ...
37 Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390x-20180114T101027Z/
38 Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390x-20180114T101027Z/
39
40 Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390x-latest.tar.bz2
41 to /var/tmp/catalyst/tmp/default/stage1-s390x-20180114T101027Z/ (This may take some time) ...
42
43 tar: SELinux support is not available
44 --- Running action sequence: unpack_snapshot
45 Cleaning up invalid snapshot cache at
46 /var/tmp/catalyst/snapshot_cache/20180114T101027Z/ (This can take a long time)...
47 Unpacking portage tree (This can take a long time) ...
48 tar: SELinux support is not available
49 lockfile does not exist '/var/tmp/catalyst/snapshot_cache/20180114T101027Z/.catalyst_lock'
50 --- Running action sequence: setup_confdir
51 Configuring /etc/portage...
52 --- Running action sequence: portage_overlay
53 --- Running action sequence: base_dirs
54 --- Running action sequence: bind
55 --- Running action sequence: chroot_setup
56 Setting up chroot...
57
58 Warning!!!!
59 Overriding certain env variables may cause catastrophic failure.
60 If your build fails look here first as the possible problem.
61 Catalyst assumes you know what you are doing when setting
62 these variables.
63 Catalyst Maintainers use VERY minimal envscripts if used at all
64 You have been warned
65
66 --- Running action sequence: setup_environment
67 --- Running action sequence: run_local
68 copying make.conf to /var/tmp/catalyst/tmp/default/stage1-s390x-20180114T101027Z///tmp/stage1root/etc/portage
69 Copying stage1-chroot.sh to /tmp
70 copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-s390x-20180114T101027Z//tmp
71 copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-s390x-20180114T101027Z//tmp
72 Ensure the file has the executable bit set
73 Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-s390x-20180114T101027Z/
74 >>> Regenerating /etc/ld.so.cache...
75 Adding USE=' build' to make.conf for portage build
76 emerge --quiet --oneshot --update --newuse sys-apps/portage
77 Updating seed stage...
78 emerge --quiet --update --deep --newuse --complete-graph --rebuild-if-new-ver gcc
79 [ebuild U ] dev-libs/gmp-6.1.2 [6.1.0]
80 [ebuild U ] dev-libs/mpfr-3.1.6 [3.1.3_p4]
81 [ebuild R ] sys-libs/cracklib-2.9.6-r1
82 [ebuild rR ] dev-libs/mpc-1.0.3
83 [ebuild rR ] sys-devel/gcc-5.4.0-r4
84 [ebuild rR ] sys-devel/gcc-4.9.4
85 [ebuild R ] sys-kernel/linux-headers-4.4
86 [ebuild R ] sys-libs/pam-1.2.1-r2
87 [ebuild R ] dev-lang/python-3.5.4-r1
88 [ebuild R ] dev-lang/python-2.7.14-r1
89
90 The following mask changes are necessary to proceed:
91 (see "package.unmask" in the portage(5) man page for more details)
92 # required by @__auto_rebuild__ (argument)
93 # /usr/portage/profiles/package.mask:
94 # Michał Górny <mgorny@g.o>, Andreas K. Hüttel <dilfridge@g.o>,
95 # Matthias Maier <tamiko@g.o> (21 May 2017)
96 # These old versions of toolchain packages (binutils, gcc, glibc) are no
97 # longer officially supported and are not suitable for general use. Using
98 # these packages can result in build failures (and possible breakage) for
99 # many packages, and may leave your system vulnerable to known security
100 # exploits.
101 # If you still use one of these old toolchain packages, please upgrade (and
102 # switch the compiler / the binutils) ASAP. If you need them for a specific
103 # (isolated) use case, feel free to unmask them on your system.
104 # (updated 27 Dec 2017 with gcc < 5.4)
105 =sys-devel/gcc-4.9.4
106
107 Use --autounmask-write to write changes to config files (honoring
108 CONFIG_PROTECT). Carefully examine the list of proposed changes,
109 paying special attention to mask or keyword changes that may expose
110 experimental or unstable packages.
111
112 !!! catalyst: run script failed.
113
114
115 Traceback (most recent call last):
116 File "modules/generic_stage_target.py", line 1244, in run_local
117 "run script failed.",env=self.env)
118 File "/usr/lib64/catalyst/modules/catalyst_support.py", line 541, in cmd
119 raise CatalystError,myexc
120 CatalystError
121 None
122
123 !!! catalyst: Stage build aborting due to error.
124
125 Traceback (most recent call last):
126 File "/usr/lib64/catalyst/catalyst", line 218, in build_target
127 mytarget.run()
128 File "modules/generic_stage_target.py", line 1304, in run
129 apply(getattr(self,x))
130 File "modules/generic_stage_target.py", line 1249, in run_local
131 raise CatalystError,"Stage build aborting due to error."
132 CatalystError
133 !!! catalyst: Error encountered during run of target stage1
134 Catalyst aborting....
135 lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-s390x-20180114T101027Z/.catalyst_lock'
136 Command exited with non-zero status 1
137 32.26user 3.72system 0:37.82elapsed 95%CPU (0avgtext+0avgdata 276976maxresident)k
138 0inputs+0outputs (358major+307341minor)pagefaults 0swaps
139
140
141
142 Full build log at /tmp/catalyst-auto.20180114T101027Z.UF8xRd/log/stage1.log