1 |
tar: gcc-4.5.3/gcc/config/vax/vax-protos.h: Cannot open: No such file or directory |
2 |
tar: gcc-4.5.3/gcc/config/vax/netbsd.h: Cannot open: No such file or directory |
3 |
tar: gcc-4.5.3/gcc/config/vax/t-linux: Cannot open: No such file or directory |
4 |
tar: gcc-4.5.3/gcc/config/vax/netbsd-elf.h: Cannot open: No such file or directory |
5 |
tar: gcc-4.5.3/gcc/config/vax/elf.h: Cannot open: No such file or directory |
6 |
tar: gcc-4.5.3/gcc/config/vax/lib1funcs.asm: Cannot open: No such file or directory |
7 |
tar: gcc-4.5.3/gcc/config/vax/vax.h: Cannot open: No such file or directory |
8 |
tar: gcc-4.5.3/gcc/config/vax/openbsd1.h: Cannot open: No such file or directory |
9 |
tar: gcc-4.5.3/gcc/config/vax/constraints.md: Cannot open: No such file or directory |
10 |
tar: gcc-4.5.3/gcc/config/vax/predicates.md: Cannot open: No such file or directory |
11 |
tar: gcc-4.5.3/gcc/config/vax/builtins.md: Cannot open: No such file or directory |
12 |
tar: gcc-4.5.3/gcc/config/vax/vax.opt: Cannot open: No such file or directory |
13 |
tar: gcc-4.5.3/gcc/config/vax/vax-modes.def: Cannot open: No such file or directory |
14 |
tar: gcc-4.5.3/gcc/config/vax/linux.h: Cannot open: No such file or directory |
15 |
tar: gcc-4.5.3/gcc/config/vax/vax.c: Cannot open: No such file or directory |
16 |
tar: gcc-4.5.3/gcc/config/vax/vax.md: Cannot open: No such file or directory |
17 |
tar: gcc-4.5.3/gcc/config/vax/openbsd.h: Cannot open: No such file or directory |
18 |
tar: gcc-4.5.3/gcc/config/kopensolaris-gnu.h: Cannot open: No space left on device |
19 |
tar: gcc-4.5.3/gcc/config/memcmp.c: Cannot open: No space left on device |
20 |
tar: gcc-4.5.3/gcc/config/openbsd.h: Cannot open: No space left on device |
21 |
tar: gcc-4.5.3/gcc/config/rtems.h: Cannot open: No space left on device |
22 |
tar: gcc-4.5.3/gcc/tree-dump.h: Cannot open: No space left on device |
23 |
tar: gcc-4.5.3/gcc/tree-parloops.c: Cannot open: No space left on device |
24 |
tar: gcc-4.5.3/gcc/tree-ssa-loop-ivcanon.c: Cannot open: No space left on device |
25 |
tar: gcc-4.5.3/gcc/gthr-gnat.h: Cannot open: No space left on device |
26 |
tar: gcc-4.5.3/gcc/cselib.h: Cannot open: No space left on device |
27 |
tar: gcc-4.5.3/gcc/ddg.h: Cannot open: No space left on device |
28 |
tar: gcc-4.5.3/gcc/dwarf2out.c: Cannot open: No space left on device |
29 |
tar: gcc-4.5.3/gcc/mips-tfile.c: Cannot open: No space left on device |
30 |
tar: gcc-4.5.3/gcc/vec.h: Cannot open: No space left on device |
31 |
tar: gcc-4.5.3/gcc/collect2.c: Cannot open: No space left on device |
32 |
tar: gcc-4.5.3/gcc/loop-iv.c: Cannot open: No space left on device |
33 |
tar: gcc-4.5.3/gcc/objcp: Cannot mkdir: No space left on device |
34 |
tar: gcc-4.5.3/gcc/objcp/objcp-decl.c: Cannot open: No such file or directory |
35 |
tar: gcc-4.5.3/gcc/objcp/config-lang.in: Cannot open: No such file or directory |
36 |
tar: gcc-4.5.3/gcc/objcp/lang-specs.h: Cannot open: No such file or directory |
37 |
tar: gcc-4.5.3/gcc/objcp/ChangeLog: Cannot open: No such file or directory |
38 |
tar: gcc-4.5.3/gcc/objcp/objcp-lang.c: Cannot open: No such file or directory |
39 |
tar: gcc-4.5.3/gcc/objcp/Make-lang.in: Cannot open: No such file or directory |
40 |
tar: gcc-4.5.3/gcc/objcp/objcp-decl.h: Cannot open: No such file or directory |
41 |
tar: gcc-4.5.3/gcc/alias.h: Cannot open: No space left on device |
42 |
tar: gcc-4.5.3/gcc/store-motion.c: Cannot open: No space left on device |
43 |
tar: gcc-4.5.3/gcc/cif-code.def: Cannot open: No space left on device |
44 |
tar: gcc-4.5.3/gcc/omega.c: Cannot open: No space left on device |
45 |
tar: gcc-4.5.3/gcc/dbgcnt.def: Cannot open: No space left on device |
46 |
tar: gcc-4.5.3/gcc/crtstuff.c: Cannot open: No space left on device |
47 |
tar: gcc-4.5.3/gcc/hwint.h: Cannot open: No space left on device |
48 |
tar: gcc-4.5.3/gcc/ipa-prop.c: Cannot open: No space left on device |
49 |
tar: gcc-4.5.3/gcc/hooks.h: Cannot open: No space left on device |
50 |
tar: gcc-4.5.3/gcc/graphds.c: Cannot open: No space left on device |
51 |
tar: gcc-4.5.3/gcc/graphite.c: Cannot open: No space left on device |
52 |
tar: gcc-4.5.3/gcc/tree-flow.h: Cannot open: No space left on device |
53 |
tar: gcc-4.5.3/gcc/recog.h: Cannot open: No space left on device |
54 |
tar: gcc-4.5.3/gcc/plugin.def: Cannot open: No space left on device |
55 |
tar: gcc-4.5.3/gcc/tree-ssa-phiprop.c: Cannot open: No space left on device |
56 |
tar: gcc-4.5.3/gcc/gsstruct.def: Cannot open: No space left on device |
57 |
tar: gcc-4.5.3/gcc/combine.c: Cannot open: No space left on device |
58 |
tar: gcc-4.5.3/gcc/input.h: Cannot open: No space left on device |
59 |
tar: gcc-4.5.3/ltsugar.m4: Cannot open: No space left on device |
60 |
tar: Exiting with failure status due to previous errors |
61 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
62 |
* ERROR: sys-devel/gcc-4.5.3-r1 failed (unpack phase): |
63 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
64 |
* failure unpacking gcc-4.5.3.tar.bz2 |
65 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
66 |
* |
67 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
68 |
* Call stack: |
69 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
70 |
* ebuild.sh, line 56: Called src_unpack |
71 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
72 |
* environment, line 4589: Called toolchain_src_unpack |
73 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
74 |
* environment, line 5402: Called gcc_quick_unpack |
75 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
76 |
* environment, line 2823: Called unpack 'gcc-4.5.3.tar.bz2' |
77 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
78 |
* ebuild.sh, line 401: Called _unpack_tar 'bzip2 -d' |
79 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
80 |
* ebuild.sh, line 371: Called assert_sigpipe_ok 'failure unpacking gcc-4.5.3.tar.bz2' |
81 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
82 |
* isolated-functions.sh, line 37: Called die |
83 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
84 |
* The specific snippet of code: |
85 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
86 |
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@" |
87 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
88 |
* |
89 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
90 |
* If you need support, post the output of 'emerge --info =sys-devel/gcc-4.5.3-r1', |
91 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
92 |
* the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.5.3-r1'. |
93 |
/usr/lib/portage/bin/isolated-functions.sh: line 211: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/.die_hooks: No space left on device |
94 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
95 |
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/build.log'. |
96 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
97 |
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment'. |
98 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device |
99 |
* S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3' |
100 |
Traceback (most recent call last): |
101 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 276, in <module> |
102 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
103 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main |
104 |
return ebuild_ipc.communicate(args) |
105 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate |
106 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
107 |
File "/usr/lib/portage/pym/portage/locks.py", line 73, in lockfile |
108 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
109 |
File "/usr/lib/portage/pym/portage/__init__.py", line 215, in __call__ |
110 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
111 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/.ipc_lock' |
112 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
113 |
* is known to be triggered by things such as failed variable assignments |
114 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
115 |
* exiting, bash should have displayed an error message above. If bash did |
116 |
* not produce an error message above, it's possible that the ebuild has |
117 |
* called `exit` when it should have called `die` instead. This behavior |
118 |
* may also be triggered by a corrupt bash binary or a hardware problem |
119 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
120 |
* it appears to occur randomly, then it is likely to be triggered by a |
121 |
* hardware problem. If you suspect a hardware problem then you should try |
122 |
* some basic hardware diagnostics such as memtest. Please do not report |
123 |
* this as a bug unless it is consistently reproducible and you are sure |
124 |
* that your bash binary and hardware are functioning properly. |
125 |
/usr/lib/portage/bin/misc-functions.sh: line 978: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/.die_hooks: No space left on device |
126 |
Traceback (most recent call last): |
127 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 276, in <module> |
128 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
129 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main |
130 |
return ebuild_ipc.communicate(args) |
131 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate |
132 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
133 |
File "/usr/lib/portage/pym/portage/locks.py", line 73, in lockfile |
134 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
135 |
File "/usr/lib/portage/pym/portage/__init__.py", line 215, in __call__ |
136 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
137 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/.ipc_lock' |
138 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
139 |
* behavior is known to be triggered by things such as failed variable |
140 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
141 |
* Normally, before exiting, bash should have displayed an error message |
142 |
* above. If bash did not produce an error message above, it's possible |
143 |
* that the ebuild has called `exit` when it should have called `die` |
144 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
145 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
146 |
* not reproducible or it appears to occur randomly, then it is likely to |
147 |
* be triggered by a hardware problem. If you suspect a hardware problem |
148 |
* then you should try some basic hardware diagnostics such as memtest. |
149 |
* Please do not report this as a bug unless it is consistently |
150 |
* reproducible and you are sure that your bash binary and hardware are |
151 |
* functioning properly. |
152 |
|
153 |
* Messages for package sys-kernel/linux-headers-2.6.36.1: |
154 |
* Note: Even though you have successfully unmerged |
155 |
* your kernel package, directories in kernel source location: |
156 |
* /usr/src/linux-2.6.36.1 |
157 |
* with modified files will remain behind. By design, package managers |
158 |
* will not remove these modified files and the directories they reside in. |
159 |
|
160 |
|
161 |
* Messages for package sys-devel/gcc-4.5.3-r1: |
162 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
163 |
* is known to be triggered by things such as failed variable assignments |
164 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
165 |
* exiting, bash should have displayed an error message above. If bash did |
166 |
* not produce an error message above, it's possible that the ebuild has |
167 |
* called `exit` when it should have called `die` instead. This behavior |
168 |
* may also be triggered by a corrupt bash binary or a hardware problem |
169 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
170 |
* it appears to occur randomly, then it is likely to be triggered by a |
171 |
* hardware problem. If you suspect a hardware problem then you should try |
172 |
* some basic hardware diagnostics such as memtest. Please do not report |
173 |
* this as a bug unless it is consistently reproducible and you are sure |
174 |
* that your bash binary and hardware are functioning properly. |
175 |
|
176 |
|
177 |
!!! catalyst: run script failed. |
178 |
|
179 |
|
180 |
Traceback (most recent call last): |
181 |
File "modules/generic_stage_target.py", line 1207, in run_local |
182 |
"run script failed.",env=self.env) |
183 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, 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 209, in build_target |
192 |
mytarget.run() |
193 |
File "modules/generic_stage_target.py", line 1263, in run |
194 |
apply(getattr(self,x)) |
195 |
File "modules/generic_stage_target.py", line 1212, in run_local |
196 |
raise CatalystError,"Stage build aborting due to error." |
197 |
CatalystError |
198 |
!!! catalyst: Error encountered during run of target stage2 |
199 |
Catalyst aborting.... |
200 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage2-ia64-20111122/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.11232/log/stage2.log |