1 |
tar: gcc-4.6.3/gcc/host-default.c: Cannot open: No space left on device |
2 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
3 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
4 |
tar: gcc-4.6.3/gcc/objcp/objcp-lang.c: Cannot open: No such file or directory |
5 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
6 |
tar: gcc-4.6.3/gcc/objcp/ChangeLog: Cannot open: No such file or directory |
7 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
8 |
tar: gcc-4.6.3/gcc/objcp/config-lang.in: Cannot open: No such file or directory |
9 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
10 |
tar: gcc-4.6.3/gcc/objcp/lang-specs.h: Cannot open: No such file or directory |
11 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
12 |
tar: gcc-4.6.3/gcc/objcp/objcp-decl.c: Cannot open: No such file or directory |
13 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
14 |
tar: gcc-4.6.3/gcc/objcp/objcp-decl.h: Cannot open: No such file or directory |
15 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
16 |
tar: gcc-4.6.3/gcc/objcp/Make-lang.in: Cannot open: No such file or directory |
17 |
tar: gcc-4.6.3/gcc/cppdefault.h: Cannot open: No space left on device |
18 |
tar: gcc-4.6.3/gcc/gimple-iterator.c: Cannot open: No space left on device |
19 |
tar: gcc-4.6.3/gcc/tree-into-ssa.c: Cannot open: No space left on device |
20 |
tar: gcc-4.6.3/gcc/tree-chrec.h: Cannot open: No space left on device |
21 |
tar: gcc-4.6.3/ylwrap: Cannot open: No space left on device |
22 |
tar: gcc-4.6.3/MD5SUMS: Cannot open: No space left on device |
23 |
tar: Exiting with failure status due to previous errors |
24 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
25 |
* ERROR: sys-devel/gcc-4.6.3 failed (unpack phase): |
26 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
27 |
* failure unpacking gcc-4.6.3.tar.bz2 |
28 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
29 |
* |
30 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
31 |
* Call stack: |
32 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
33 |
* ebuild.sh, line 93: Called src_unpack |
34 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
35 |
* environment, line 4195: Called toolchain_src_unpack |
36 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
37 |
* environment, line 4949: Called gcc_quick_unpack |
38 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
39 |
* environment, line 2490: Called unpack 'gcc-4.6.3.tar.bz2' |
40 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
41 |
* phase-helpers.sh, line 345: Called __unpack_tar 'bzip2 -d' |
42 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
43 |
* phase-helpers.sh, line 315: Called __assert_sigpipe_ok 'failure unpacking gcc-4.6.3.tar.bz2' |
44 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
45 |
* isolated-functions.sh, line 39: Called die |
46 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
47 |
* The specific snippet of code: |
48 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
49 |
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@" |
50 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
51 |
* |
52 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
53 |
* If you need support, post the output of `emerge --info '=sys-devel/gcc-4.6.3'`, |
54 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
55 |
* the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3'`. |
56 |
/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4757: pushd: /var/tmp/portage/sys-devel/gcc-4.6.3/work/build: No such file or directory |
57 |
tar: Cowardly refusing to create an empty archive |
58 |
Try `tar --help' or `tar --usage' for more information. |
59 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
60 |
* |
61 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
62 |
* Please include /var/tmp/portage/sys-devel/gcc-4.6.3/work/gcc-build-logs.tar.bz2 in your bug report |
63 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
64 |
* |
65 |
/usr/lib/portage/bin/isolated-functions.sh: line 217: /var/tmp/portage/sys-devel/gcc-4.6.3/.die_hooks: No space left on device |
66 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
67 |
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'. |
68 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
69 |
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment'. |
70 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
71 |
* Working directory: '/var/tmp/portage/sys-devel/gcc-4.6.3/work' |
72 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
73 |
* S: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/gcc-4.6.3' |
74 |
Traceback (most recent call last): |
75 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 228, in <module> |
76 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
77 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main |
78 |
return ebuild_ipc.communicate(args) |
79 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 82, in communicate |
80 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
81 |
File "/usr/lib/portage/pym/portage/locks.py", line 103, in lockfile |
82 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
83 |
File "/usr/lib/portage/pym/portage/__init__.py", line 246, in __call__ |
84 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
85 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.6.3/.ipc_lock' |
86 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
87 |
* is known to be triggered by things such as failed variable assignments |
88 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
89 |
* exiting, bash should have displayed an error message above. If bash did |
90 |
* not produce an error message above, it's possible that the ebuild has |
91 |
* called `exit` when it should have called `die` instead. This behavior |
92 |
* may also be triggered by a corrupt bash binary or a hardware problem |
93 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
94 |
* it appears to occur randomly, then it is likely to be triggered by a |
95 |
* hardware problem. If you suspect a hardware problem then you should try |
96 |
* some basic hardware diagnostics such as memtest. Please do not report |
97 |
* this as a bug unless it is consistently reproducible and you are sure |
98 |
* that your bash binary and hardware are functioning properly. |
99 |
/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4757: pushd: /var/tmp/portage/sys-devel/gcc-4.6.3/work/build: No such file or directory |
100 |
tar: Cowardly refusing to create an empty archive |
101 |
Try `tar --help' or `tar --usage' for more information. |
102 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device |
103 |
* |
104 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device |
105 |
* Please include /var/tmp/portage/sys-devel/gcc-4.6.3/gcc-build-logs.tar.bz2 in your bug report |
106 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device |
107 |
* |
108 |
/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4762: popd: directory stack empty |
109 |
/usr/lib/portage/bin/misc-functions.sh: line 1245: /var/tmp/portage/sys-devel/gcc-4.6.3/.die_hooks: No space left on device |
110 |
Traceback (most recent call last): |
111 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 228, in <module> |
112 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
113 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main |
114 |
return ebuild_ipc.communicate(args) |
115 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 82, in communicate |
116 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
117 |
File "/usr/lib/portage/pym/portage/locks.py", line 103, in lockfile |
118 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
119 |
File "/usr/lib/portage/pym/portage/__init__.py", line 246, in __call__ |
120 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
121 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.6.3/.ipc_lock' |
122 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
123 |
* behavior is known to be triggered by things such as failed variable |
124 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
125 |
* Normally, before exiting, bash should have displayed an error message |
126 |
* above. If bash did not produce an error message above, it's possible |
127 |
* that the ebuild has called `exit` when it should have called `die` |
128 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
129 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
130 |
* not reproducible or it appears to occur randomly, then it is likely to |
131 |
* be triggered by a hardware problem. If you suspect a hardware problem |
132 |
* then you should try some basic hardware diagnostics such as memtest. |
133 |
* Please do not report this as a bug unless it is consistently |
134 |
* reproducible and you are sure that your bash binary and hardware are |
135 |
* functioning properly. |
136 |
* Messages for package sys-libs/timezone-data-2013b merged to /tmp/stage1root/: |
137 |
* You do not have TIMEZONE set in /tmp/stage1root/etc/timezone. |
138 |
* Setting /tmp/stage1root/etc/localtime to Factory. |
139 |
* Messages for package sys-apps/coreutils-8.20 merged to /tmp/stage1root/: |
140 |
* Make sure you run 'hash -r' in your active shells. |
141 |
* You should also re-source your shell settings for LS_COLORS |
142 |
* changes, such as: source /etc/profile |
143 |
* Messages for package sys-apps/util-linux-2.22.2 merged to /tmp/stage1root/: |
144 |
* The agetty util now clears the terminal by default. You |
145 |
* might want to add --noclear to your /etc/inittab lines. |
146 |
* Messages for package sys-libs/glibc-2.15-r3 merged to /tmp/stage1root/: |
147 |
* Defaulting /etc/host.conf:multi to on |
148 |
* Messages for package sys-devel/gcc-4.6.3 merged to /tmp/stage1root/: |
149 |
* |
150 |
* LTO support is still experimental and unstable. |
151 |
* Any bugs resulting from the use of LTO will not be fixed. |
152 |
* |
153 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
154 |
* is known to be triggered by things such as failed variable assignments |
155 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
156 |
* exiting, bash should have displayed an error message above. If bash did |
157 |
* not produce an error message above, it's possible that the ebuild has |
158 |
* called `exit` when it should have called `die` instead. This behavior |
159 |
* may also be triggered by a corrupt bash binary or a hardware problem |
160 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
161 |
* it appears to occur randomly, then it is likely to be triggered by a |
162 |
* hardware problem. If you suspect a hardware problem then you should try |
163 |
* some basic hardware diagnostics such as memtest. Please do not report |
164 |
* this as a bug unless it is consistently reproducible and you are sure |
165 |
* that your bash binary and hardware are functioning properly. |
166 |
|
167 |
|
168 |
|
169 |
|
170 |
|
171 |
|
172 |
|
173 |
|
174 |
|
175 |
|
176 |
|
177 |
!!! catalyst: run script failed. |
178 |
|
179 |
|
180 |
Traceback (most recent call last): |
181 |
File "modules/generic_stage_target.py", line 1230, in run_local |
182 |
"run script failed.",env=self.env) |
183 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, in cmd |
184 |
raise CatalystError,myexc |
185 |
CatalystError |
186 |
None |
187 |
|
188 |
!!! catalyst: Stage build aborting due to error. |
189 |
|
190 |
Traceback (most recent call last): |
191 |
File "/usr/lib/catalyst/catalyst", line 214, in build_target |
192 |
mytarget.run() |
193 |
File "modules/generic_stage_target.py", line 1290, in run |
194 |
apply(getattr(self,x)) |
195 |
File "modules/generic_stage_target.py", line 1235, in run_local |
196 |
raise CatalystError,"Stage build aborting due to error." |
197 |
CatalystError |
198 |
!!! catalyst: Error encountered during run of target stage1 |
199 |
Catalyst aborting.... |
200 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-ia64-20130430/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.29009/log/stage1.log |