1 |
Using command line specified Catalyst configuration file, /etc/catalyst/release/x86-auto.conf |
2 |
Setting sharedir to config file value "/usr/lib64/catalyst/" |
3 |
Setting snapshot_cache to config file value "/release/tmp/snapshots" |
4 |
Setting hash_function to config file value "crc32" |
5 |
Setting storedir to config file value "/release/buildroot/x86-dev" |
6 |
Setting portdir to config file value "/release/trees/portage-auto" |
7 |
Setting distdir to config file value "/release/tmp/distfiles/" |
8 |
Setting options to config file value "autoresume bindist pkgcache preserve_libs seedcache snapcache" |
9 |
Autoresuming support enabled. |
10 |
Binary redistribution enabled |
11 |
Package cache support enabled. |
12 |
Preserving libs during unmerge. |
13 |
Seed cache support enabled. |
14 |
Snapshot cache support enabled. |
15 |
Envscript support enabled. |
16 |
Using target: stage1 |
17 |
Building on amd64 for alternate personality type x86 |
18 |
stage1 root path is /tmp/stage1root |
19 |
Source path set to /release/buildroot/x86-dev/builds/hardened/stage3-i686-hardened-latest.tar.bz2 |
20 |
Caching snapshot to /release/tmp/snapshots/20170905/ |
21 |
The autoresume path is /release/buildroot/x86-dev/tmp/hardened/.autoresume-stage1-i686-hardened-20170905/ |
22 |
stage1 stage path is /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905/tmp/stage1root |
23 |
Location of the package cache is /release/buildroot/x86-dev/packages/hardened/stage1-i686-hardened-20170905/ |
24 |
Checking for processes running in chroot and killing them. |
25 |
Removing AutoResume Points: ... |
26 |
Emptying directory /release/buildroot/x86-dev/tmp/hardened/.autoresume-stage1-i686-hardened-20170905/ |
27 |
>>> Waiting 10 seconds before starting... |
28 |
>>> (Control-C to abort)... |
29 |
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 |
30 |
clearing autoresume ... |
31 |
Removing AutoResume Points: ... |
32 |
Emptying directory /release/buildroot/x86-dev/tmp/hardened/.autoresume-stage1-i686-hardened-20170905/ |
33 |
clearing chroot ... |
34 |
Emptying directory /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905/ |
35 |
clearing package cache ... |
36 |
purging the pkgcache ... |
37 |
clearing kerncache ... |
38 |
--- Running action sequence: unpack |
39 |
Referenced SEEDCACHE does not appear to be a directory, trying to untar... |
40 |
No Valid Resume point detected, cleaning up... |
41 |
Removing AutoResume Points: ... |
42 |
Emptying directory /release/buildroot/x86-dev/tmp/hardened/.autoresume-stage1-i686-hardened-20170905/ |
43 |
Emptying directory /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905/ |
44 |
|
45 |
Starting tar extract from /release/buildroot/x86-dev/builds/hardened/stage3-i686-hardened-latest.tar.bz2 |
46 |
to /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905/ (This may take some time) ... |
47 |
|
48 |
tar: SELinux support is not available |
49 |
--- Running action sequence: unpack_snapshot |
50 |
Valid snapshot cache, skipping unpack of portage tree... |
51 |
--- Running action sequence: setup_confdir |
52 |
Configuring /etc/portage... |
53 |
--- Running action sequence: portage_overlay |
54 |
--- Running action sequence: base_dirs |
55 |
--- Running action sequence: bind |
56 |
--- Running action sequence: chroot_setup |
57 |
Setting up chroot... |
58 |
|
59 |
Warning!!!! |
60 |
Overriding certain env variables may cause catastrophic failure. |
61 |
If your build fails look here first as the possible problem. |
62 |
Catalyst assumes you know what you are doing when setting |
63 |
these variables. |
64 |
Catalyst Maintainers use VERY minimal envscripts if used at all |
65 |
You have been warned |
66 |
|
67 |
--- Running action sequence: setup_environment |
68 |
--- Running action sequence: run_local |
69 |
copying make.conf to /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905///tmp/stage1root/etc/portage |
70 |
Copying stage1-chroot.sh to /tmp |
71 |
copying stage1-chroot.sh to /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905//tmp |
72 |
copying chroot-functions.sh to /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905//tmp |
73 |
Ensure the file has the executable bit set |
74 |
Running stage1-chroot.sh in chroot /release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905/ |
75 |
>>> Regenerating /etc/ld.so.cache... |
76 |
Adding USE=" build" to make.conf for portage build |
77 |
emerge --quiet --oneshot --update --newuse sys-apps/portage |
78 |
|
79 |
Performing Global Updates |
80 |
(Could take a couple of minutes if you have a lot of binary packages.) |
81 |
|
82 |
|
83 |
>>> Verifying ebuild manifests |
84 |
>>> Emerging (1 of 1) sys-apps/portage-2.3.6::gentoo |
85 |
>>> Failed to emerge sys-apps/portage-2.3.6, Log file: |
86 |
>>> '/var/tmp/portage/sys-apps/portage-2.3.6/temp/build.log' |
87 |
* Package: sys-apps/portage-2.3.6 |
88 |
* Repository: gentoo |
89 |
* Maintainer: dev-portage@g.o |
90 |
* Upstream: dev-portage@g.o |
91 |
* USE: abi_x86_32 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_4 userland_GNU x86 xattr |
92 |
* FEATURES: preserve-libs sandbox userpriv usersandbox |
93 |
/usr/bin/install: cannot change permissions of '/var/tmp/portage/sys-apps/portage-2.3.6/work': No such file or directory |
94 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
95 |
* ERROR: sys-apps/portage-2.3.6::gentoo failed (unpack phase): |
96 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
97 |
* Failed to create dir '/var/tmp/portage/sys-apps/portage-2.3.6/work' |
98 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
99 |
* |
100 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
101 |
* Call stack: |
102 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
103 |
* ebuild.sh, line 767: Called __ebuild_main 'unpack' |
104 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
105 |
* phase-functions.sh, line 1008: Called __dyn_unpack |
106 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
107 |
* phase-functions.sh, line 240: Called die |
108 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
109 |
* The specific snippet of code: |
110 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
111 |
* install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'" |
112 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
113 |
* |
114 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
115 |
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.6::gentoo'`, |
116 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
117 |
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.6::gentoo'`. |
118 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
119 |
* The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.3.6/temp/build.log'. |
120 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
121 |
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.6/temp/environment'. |
122 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
123 |
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.6/homedir' |
124 |
/var/tmp/portage/._portage_reinstall_.0uono614/bin/isolated-functions.sh: line 264: echo: write error: No space left on device |
125 |
* S: '/var/tmp/portage/sys-apps/portage-2.3.6/work/portage-2.3.6' |
126 |
Traceback (most recent call last): |
127 |
File "/var/tmp/portage/._portage_reinstall_.0uono614/bin/ebuild-ipc.py", line 282, in <module> |
128 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
129 |
File "/var/tmp/portage/._portage_reinstall_.0uono614/bin/ebuild-ipc.py", line 279, in ebuild_ipc_main |
130 |
return ebuild_ipc.communicate(args) |
131 |
File "/var/tmp/portage/._portage_reinstall_.0uono614/bin/ebuild-ipc.py", line 136, in communicate |
132 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
133 |
File "/var/tmp/portage/._portage_reinstall_.0uono614/pym/portage/locks.py", line 194, in lockfile |
134 |
locking_method = portage._eintr_func_wrapper(_get_lock_fn()) |
135 |
File "/var/tmp/portage/._portage_reinstall_.0uono614/pym/portage/locks.py", line 62, in _get_lock_fn |
136 |
fd, lock_path = tempfile.mkstemp() |
137 |
File "/usr/lib/python3.4/tempfile.py", line 271, in mkstemp |
138 |
dir = gettempdir() |
139 |
File "/usr/lib/python3.4/tempfile.py", line 239, in gettempdir |
140 |
tempdir = _get_default_tempdir() |
141 |
File "/usr/lib/python3.4/tempfile.py", line 180, in _get_default_tempdir |
142 |
dirlist) |
143 |
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/var/tmp/portage/sys-apps/portage-2.3.6/temp', '/var/tmp/portage/sys-apps/portage-2.3.6/temp', '/var/tmp/portage/sys-apps/portage-2.3.6/temp', '/tmp', '/var/tmp', '/usr/tmp', '/var/tmp/portage/._portage_reinstall_.0uono614/pym'] |
144 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
145 |
* is known to be triggered by things such as failed variable assignments |
146 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
147 |
* exiting, bash should have displayed an error message above. If bash did |
148 |
* not produce an error message above, it's possible that the ebuild has |
149 |
* called `exit` when it should have called `die` instead. This behavior |
150 |
* may also be triggered by a corrupt bash binary or a hardware problem |
151 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
152 |
* it appears to occur randomly, then it is likely to be triggered by a |
153 |
* hardware problem. If you suspect a hardware problem then you should try |
154 |
* some basic hardware diagnostics such as memtest. Please do not report |
155 |
* this as a bug unless it is consistently reproducible and you are sure |
156 |
* that your bash binary and hardware are functioning properly. |
157 |
* Messages for package sys-apps/portage-2.3.6: |
158 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
159 |
* is known to be triggered by things such as failed variable assignments |
160 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
161 |
* exiting, bash should have displayed an error message above. If bash did |
162 |
* not produce an error message above, it's possible that the ebuild has |
163 |
* called `exit` when it should have called `die` instead. This behavior |
164 |
* may also be triggered by a corrupt bash binary or a hardware problem |
165 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
166 |
* it appears to occur randomly, then it is likely to be triggered by a |
167 |
* hardware problem. If you suspect a hardware problem then you should try |
168 |
* some basic hardware diagnostics such as memtest. Please do not report |
169 |
* this as a bug unless it is consistently reproducible and you are sure |
170 |
* that your bash binary and hardware are functioning properly. |
171 |
|
172 |
|
173 |
|
174 |
!!! catalyst: run script failed. |
175 |
|
176 |
|
177 |
Traceback (most recent call last): |
178 |
File "modules/generic_stage_target.py", line 1253, in run_local |
179 |
"run script failed.",env=self.env) |
180 |
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd |
181 |
raise CatalystError,myexc |
182 |
CatalystError |
183 |
None |
184 |
|
185 |
!!! catalyst: Stage build aborting due to error. |
186 |
|
187 |
Traceback (most recent call last): |
188 |
File "/usr/lib64/catalyst/catalyst", line 218, in build_target |
189 |
mytarget.run() |
190 |
File "modules/generic_stage_target.py", line 1333, in run |
191 |
apply(getattr(self,x)) |
192 |
File "modules/generic_stage_target.py", line 1258, in run_local |
193 |
raise CatalystError,"Stage build aborting due to error." |
194 |
CatalystError |
195 |
!!! catalyst: Error encountered during run of target stage1 |
196 |
Catalyst aborting.... |
197 |
lockfile does not exist '/release/buildroot/x86-dev/tmp/hardened/stage1-i686-hardened-20170905/.catalyst_lock' |
198 |
Command exited with non-zero status 1 |
199 |
36.12user 5.72system 0:30.17elapsed 138%CPU (0avgtext+0avgdata 771104maxresident)k |
200 |
68984inputs+1796384outputs (0major+277766minor)pagefaults 0swaps |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /release/tmp/run/catalyst-auto.20170905.kKb518/log/hardened_stage1.log |