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/lib/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-s390-latest.tar.bz2 |
25 |
Caching snapshot to /var/tmp/catalyst/snapshot_cache/20161117/ |
26 |
The autoresume path is /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161117/ |
27 |
stage1 stage path is /var/tmp/catalyst/tmp/default/stage1-s390-20161117/tmp/stage1root |
28 |
Location of the package cache is /var/tmp/catalyst/packages/default/stage1-s390-20161117/ |
29 |
Location of the kerncache is /var/tmp/catalyst/kerncache/default/stage1-s390-20161117/ |
30 |
Checking for processes running in chroot and killing them. |
31 |
Removing AutoResume Points: ... |
32 |
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161117/ |
33 |
>>> Waiting 10 seconds before starting... |
34 |
>>> (Control-C to abort)... |
35 |
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 |
36 |
clearing autoresume ... |
37 |
Removing AutoResume Points: ... |
38 |
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161117/ |
39 |
clearing chroot ... |
40 |
Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390-20161117/ |
41 |
clearing package cache ... |
42 |
purging the pkgcache ... |
43 |
clearing kerncache ... |
44 |
purging the kerncache ... |
45 |
--- Running action sequence: unpack |
46 |
Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
47 |
No Valid Resume point detected, cleaning up... |
48 |
Removing AutoResume Points: ... |
49 |
Emptying directory /var/tmp/catalyst/tmp/default/.autoresume-stage1-s390-20161117/ |
50 |
Emptying directory /var/tmp/catalyst/tmp/default/stage1-s390-20161117/ |
51 |
|
52 |
Starting tar extract from /var/tmp/catalyst/builds/default/stage3-s390-latest.tar.bz2 |
53 |
to /var/tmp/catalyst/tmp/default/stage1-s390-20161117/ (This may take some time) ... |
54 |
|
55 |
tar: SELinux support is not available |
56 |
--- Running action sequence: unpack_snapshot |
57 |
Cleaning up invalid snapshot cache at |
58 |
/var/tmp/catalyst/snapshot_cache/20161117/ (This can take a long time)... |
59 |
Unpacking portage tree (This can take a long time) ... |
60 |
tar: SELinux support is not available |
61 |
lockfile does not exist '/var/tmp/catalyst/snapshot_cache/20161117/.catalyst_lock' |
62 |
--- Running action sequence: setup_confdir |
63 |
Configuring /etc/portage... |
64 |
--- Running action sequence: portage_overlay |
65 |
--- Running action sequence: base_dirs |
66 |
--- Running action sequence: bind |
67 |
--- Running action sequence: chroot_setup |
68 |
Setting up chroot... |
69 |
|
70 |
Warning!!!! |
71 |
Overriding certain env variables may cause catastrophic failure. |
72 |
If your build fails look here first as the possible problem. |
73 |
Catalyst assumes you know what you are doing when setting |
74 |
these variables. |
75 |
Catalyst Maintainers use VERY minimal envscripts if used at all |
76 |
You have been warned |
77 |
|
78 |
--- Running action sequence: setup_environment |
79 |
--- Running action sequence: run_local |
80 |
copying make.conf to /var/tmp/catalyst/tmp/default/stage1-s390-20161117///tmp/stage1root/etc/portage |
81 |
Copying stage1-chroot.sh to /tmp |
82 |
copying stage1-chroot.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20161117//tmp |
83 |
copying chroot-functions.sh to /var/tmp/catalyst/tmp/default/stage1-s390-20161117//tmp |
84 |
Ensure the file has the executable bit set |
85 |
Running stage1-chroot.sh in chroot /var/tmp/catalyst/tmp/default/stage1-s390-20161117/ |
86 |
>>> Regenerating /etc/ld.so.cache... |
87 |
Adding USE=' build' to make.conf for portage build |
88 |
emerge --quiet --oneshot --update --newuse sys-apps/portage |
89 |
|
90 |
Performing Global Updates |
91 |
(Could take a couple of minutes if you have a lot of binary packages.) |
92 |
|
93 |
|
94 |
|
95 |
The following packages are causing rebuilds: |
96 |
|
97 |
(sys-libs/ncurses-6.0-r1:0/6::gentoo, ebuild scheduled for merge) causes rebuilds for: |
98 |
(sys-apps/less-481:0/0::gentoo, ebuild scheduled for merge) |
99 |
(sys-apps/util-linux-2.26.2:0/0::gentoo, ebuild scheduled for merge) |
100 |
(app-editors/nano-2.5.3:0/0::gentoo, ebuild scheduled for merge) |
101 |
(sys-devel/gettext-0.19.7:0/0::gentoo, ebuild scheduled for merge) |
102 |
(sys-apps/openrc-0.19.1:0/0::gentoo, ebuild scheduled for merge) |
103 |
>>> Verifying ebuild manifests |
104 |
>>> Emerging (1 of 9) sys-libs/ncurses-6.0-r1::gentoo |
105 |
>>> Installing (1 of 9) sys-libs/ncurses-6.0-r1::gentoo |
106 |
>>> Emerging (2 of 9) sys-process/runit-2.1.1-r1::gentoo |
107 |
>>> Failed to emerge sys-process/runit-2.1.1-r1 |
108 |
|
109 |
* Messages for package sys-libs/ncurses-6.0-r1: |
110 |
|
111 |
* The ebuild phase 'other' has exited unexpectedly. This type of behavior |
112 |
* is known to be triggered by things such as failed variable assignments |
113 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
114 |
* exiting, bash should have displayed an error message above. If bash did |
115 |
* not produce an error message above, it's possible that the ebuild has |
116 |
* called `exit` when it should have called `die` instead. This behavior |
117 |
* may also be triggered by a corrupt bash binary or a hardware problem |
118 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
119 |
* it appears to occur randomly, then it is likely to be triggered by a |
120 |
* hardware problem. If you suspect a hardware problem then you should try |
121 |
* some basic hardware diagnostics such as memtest. Please do not report |
122 |
* this as a bug unless it is consistently reproducible and you are sure |
123 |
* that your bash binary and hardware are functioning properly. |
124 |
|
125 |
* Messages for package sys-process/runit-2.1.1-r1: |
126 |
|
127 |
|
128 |
!!! catalyst: run script failed. |
129 |
|
130 |
|
131 |
Traceback (most recent call last): |
132 |
File "modules/generic_stage_target.py", line 1244, in run_local |
133 |
"run script failed.",env=self.env) |
134 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd |
135 |
raise CatalystError,myexc |
136 |
CatalystError |
137 |
None |
138 |
|
139 |
!!! catalyst: Stage build aborting due to error. |
140 |
|
141 |
Traceback (most recent call last): |
142 |
File "/usr/lib/catalyst/catalyst", line 218, in build_target |
143 |
mytarget.run() |
144 |
File "modules/generic_stage_target.py", line 1304, in run |
145 |
apply(getattr(self,x)) |
146 |
File "modules/generic_stage_target.py", line 1249, in run_local |
147 |
raise CatalystError,"Stage build aborting due to error." |
148 |
CatalystError |
149 |
!!! catalyst: Error encountered during run of target stage1 |
150 |
Catalyst aborting.... |
151 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-s390-20161117/.catalyst_lock' |
152 |
Command exited with non-zero status 1 |
153 |
387.35user 151.84system 8:20.46elapsed 107%CPU (0avgtext+0avgdata 193552maxresident)k |
154 |
0inputs+0outputs (669major+31755264minor)pagefaults 0swaps |
155 |
|
156 |
|
157 |
|
158 |
Full build log at /tmp/catalyst-auto.20161117.9TEXFc/log/stage1.log |