1 |
Setting hash_function to config file value "crc32" |
2 |
Setting storedir to config file value "/release/buildroot/amd64-dev" |
3 |
Setting portdir to config file value "/release/trees/portage-auto" |
4 |
Setting distdir to config file value "/release/tmp/distfiles/" |
5 |
Setting options to config file value "autoresume bindist pkgcache preserve_libs seedcache snapcache" |
6 |
Autoresuming support enabled. |
7 |
Binary redistribution enabled |
8 |
Package cache support enabled. |
9 |
Preserving libs during unmerge. |
10 |
Seed cache support enabled. |
11 |
Snapshot cache support enabled. |
12 |
Envscript support enabled. |
13 |
Using target: stage4 |
14 |
Building natively for amd64 |
15 |
Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2 |
16 |
Caching snapshot to /release/tmp/snapshots/20170831/ |
17 |
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/ |
18 |
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/ |
19 |
Checking for processes running in chroot and killing them. |
20 |
Removing AutoResume Points: ... |
21 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/ |
22 |
>>> Waiting 10 seconds before starting... |
23 |
>>> (Control-C to abort)... |
24 |
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1 |
25 |
clearing autoresume ... |
26 |
Removing AutoResume Points: ... |
27 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/ |
28 |
clearing chroot ... |
29 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/ |
30 |
clearing package cache ... |
31 |
purging the pkgcache ... |
32 |
clearing kerncache ... |
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 /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/ |
38 |
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/ |
39 |
|
40 |
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2 |
41 |
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/ (This may take some time) ... |
42 |
|
43 |
tar: SELinux support is not available |
44 |
--- Running action sequence: unpack_snapshot |
45 |
Valid snapshot cache, skipping unpack of portage tree... |
46 |
--- Running action sequence: config_profile_link |
47 |
Configuring profile link... |
48 |
--- Running action sequence: setup_confdir |
49 |
Configuring /etc/portage... |
50 |
--- Running action sequence: portage_overlay |
51 |
--- Running action sequence: bind |
52 |
--- Running action sequence: chroot_setup |
53 |
Setting up chroot... |
54 |
|
55 |
Warning!!!! |
56 |
Overriding certain env variables may cause catastrophic failure. |
57 |
If your build fails look here first as the possible problem. |
58 |
Catalyst assumes you know what you are doing when setting |
59 |
these variables. |
60 |
Catalyst Maintainers use VERY minimal envscripts if used at all |
61 |
You have been warned |
62 |
|
63 |
--- Running action sequence: setup_environment |
64 |
--- Running action sequence: build_packages |
65 |
Copying stage4-chroot.sh to /tmp |
66 |
copying stage4-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831//tmp |
67 |
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831//tmp |
68 |
Ensure the file has the executable bit set |
69 |
Running stage4-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/ |
70 |
>>> Regenerating /etc/ld.so.cache... |
71 |
Updating portage with USE="" |
72 |
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage |
73 |
|
74 |
Performing Global Updates |
75 |
(Could take a couple of minutes if you have a lot of binary packages.) |
76 |
|
77 |
|
78 |
Bringing system up to date using profile specific use flags |
79 |
emerge --quiet --usepkg --buildpkg --newuse -u @system |
80 |
>>> Verifying ebuild manifests |
81 |
>>> Emerging (1 of 1) sys-devel/binutils-2.28.1::gentoo |
82 |
>>> Failed to emerge sys-devel/binutils-2.28.1, Log file: |
83 |
>>> '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/build.log' |
84 |
* Package: sys-devel/binutils-2.28.1 |
85 |
* Repository: gentoo |
86 |
* Maintainer: toolchain@g.o |
87 |
* USE: abi_x86_64 amd64 cxx elibc_glibc kernel_linux nls userland_GNU |
88 |
* FEATURES: preserve-libs sandbox userpriv usersandbox |
89 |
/usr/bin/install: cannot change permissions of '/var/tmp/portage/sys-devel/binutils-2.28.1/work': No such file or directory |
90 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
91 |
* ERROR: sys-devel/binutils-2.28.1::gentoo failed (unpack phase): |
92 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
93 |
* Failed to create dir '/var/tmp/portage/sys-devel/binutils-2.28.1/work' |
94 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
95 |
* |
96 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
97 |
* Call stack: |
98 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
99 |
* ebuild.sh, line 767: Called __ebuild_main 'unpack' |
100 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
101 |
* phase-functions.sh, line 1008: Called __dyn_unpack |
102 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
103 |
* phase-functions.sh, line 240: Called die |
104 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
105 |
* The specific snippet of code: |
106 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
107 |
* install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'" |
108 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
109 |
* |
110 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
111 |
* If you need support, post the output of `emerge --info '=sys-devel/binutils-2.28.1::gentoo'`, |
112 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
113 |
* the complete build log and the output of `emerge -pqv '=sys-devel/binutils-2.28.1::gentoo'`. |
114 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
115 |
* The complete build log is located at '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/build.log'. |
116 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
117 |
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/environment'. |
118 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
119 |
* Working directory: '/var/tmp/portage/sys-devel/binutils-2.28.1/homedir' |
120 |
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device |
121 |
* S: '/var/tmp/portage/sys-devel/binutils-2.28.1/work/binutils-2.28.1' |
122 |
* ACCESS DENIED: open_wr: /usr/lib64/python3.4/site-packages/aayc8gmb |
123 |
Traceback (most recent call last): |
124 |
File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 282, in <module> |
125 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
126 |
File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 279, in ebuild_ipc_main |
127 |
return ebuild_ipc.communicate(args) |
128 |
File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 136, in communicate |
129 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
130 |
File "/usr/lib64/python3.4/site-packages/portage/locks.py", line 194, in lockfile |
131 |
locking_method = portage._eintr_func_wrapper(_get_lock_fn()) |
132 |
File "/usr/lib64/python3.4/site-packages/portage/locks.py", line 62, in _get_lock_fn |
133 |
fd, lock_path = tempfile.mkstemp() |
134 |
File "/usr/lib64/python3.4/tempfile.py", line 271, in mkstemp |
135 |
dir = gettempdir() |
136 |
File "/usr/lib64/python3.4/tempfile.py", line 239, in gettempdir |
137 |
tempdir = _get_default_tempdir() |
138 |
File "/usr/lib64/python3.4/tempfile.py", line 180, in _get_default_tempdir |
139 |
dirlist) |
140 |
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/tmp', '/var/tmp', '/usr/tmp', '/usr/lib64/python3.4/site-packages'] |
141 |
* --------------------------- ACCESS VIOLATION SUMMARY --------------------------- |
142 |
* LOG FILE: "/var/log/sandbox/sandbox-18323.log" |
143 |
* -------------------------------------------------------------------------------- |
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-devel/binutils-2.28.1: |
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: Error in attempt to build packages |
175 |
|
176 |
|
177 |
Traceback (most recent call last): |
178 |
File "modules/generic_stage_target.py", line 1432, in build_packages |
179 |
"Error in attempt to build packages",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: stage4build 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 1437, in build_packages |
193 |
"build aborting due to error." |
194 |
CatalystError |
195 |
!!! catalyst: Error encountered during run of target stage4 |
196 |
Catalyst aborting.... |
197 |
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/.catalyst_lock' |
198 |
Command exited with non-zero status 1 |
199 |
34.53user 6.04system 0:24.61elapsed 164%CPU (0avgtext+0avgdata 844784maxresident)k |
200 |
3984inputs+1815176outputs (0major+292809minor)pagefaults 0swaps |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /release/tmp/run/catalyst-auto.20170831.IkLA0t/log/hardened_stage4-nomultilib-cloud.log |