1 |
tar: gcc-4.6.3/gcc/objcp: Cannot mkdir: No space left on device |
2 |
tar: gcc-4.6.3/gcc/objcp/Make-lang.in: Cannot open: No such file or directory |
3 |
tar: gcc-4.6.3/gcc/cppdefault.h: Cannot open: No space left on device |
4 |
tar: gcc-4.6.3/gcc/gimple-iterator.c: Cannot open: No space left on device |
5 |
tar: gcc-4.6.3/gcc/tree-into-ssa.c: Cannot open: No space left on device |
6 |
tar: gcc-4.6.3/gcc/tree-chrec.h: Cannot open: No space left on device |
7 |
tar: gcc-4.6.3/ylwrap: Cannot open: No space left on device |
8 |
tar: gcc-4.6.3/MD5SUMS: Cannot open: No space left on device |
9 |
tar: Exiting with failure status due to previous errors |
10 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
11 |
* ERROR: sys-devel/gcc-4.6.3::gentoo failed (unpack phase): |
12 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
13 |
* failure unpacking gcc-4.6.3.tar.bz2 |
14 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
15 |
* |
16 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
17 |
* Call stack: |
18 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
19 |
* ebuild.sh, line 93: Called src_unpack |
20 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
21 |
* environment, line 4291: Called toolchain_src_unpack |
22 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
23 |
* environment, line 5081: Called gcc_quick_unpack |
24 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
25 |
* environment, line 2592: Called unpack 'gcc-4.6.3.tar.bz2' |
26 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
27 |
* phase-helpers.sh, line 345: Called __unpack_tar 'bzip2 -d' |
28 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
29 |
* phase-helpers.sh, line 315: Called __assert_sigpipe_ok 'failure unpacking gcc-4.6.3.tar.bz2' |
30 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
31 |
* isolated-functions.sh, line 39: Called die |
32 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
33 |
* The specific snippet of code: |
34 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
35 |
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@" |
36 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
37 |
* |
38 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
39 |
* If you need support, post the output of `emerge --info '=sys-devel/gcc-4.6.3::gentoo'`, |
40 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
41 |
* the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3::gentoo'`. |
42 |
/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4882: pushd: /var/tmp/portage/sys-devel/gcc-4.6.3/work/build: No such file or directory |
43 |
tar: Cowardly refusing to create an empty archive |
44 |
Try `tar --help' or `tar --usage' for more information. |
45 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
46 |
* |
47 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
48 |
* Please include /var/tmp/portage/sys-devel/gcc-4.6.3/work/gcc-build-logs.tar.bz2 in your bug report |
49 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
50 |
* |
51 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 190: /var/tmp/portage/sys-devel/gcc-4.6.3/.die_hooks: No space left on device |
52 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
53 |
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'. |
54 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
55 |
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment'. |
56 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
57 |
* Working directory: '/var/tmp/portage/sys-devel/gcc-4.6.3/work' |
58 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/unpack: No space left on device |
59 |
* S: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/gcc-4.6.3' |
60 |
Traceback (most recent call last): |
61 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 228, in <module> |
62 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
63 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main |
64 |
return ebuild_ipc.communicate(args) |
65 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 82, in communicate |
66 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
67 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/pym/portage/locks.py", line 105, in lockfile |
68 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
69 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/pym/portage/__init__.py", line 259, in __call__ |
70 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
71 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.6.3/.ipc_lock' |
72 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
73 |
* is known to be triggered by things such as failed variable assignments |
74 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
75 |
* exiting, bash should have displayed an error message above. If bash did |
76 |
* not produce an error message above, it's possible that the ebuild has |
77 |
* called `exit` when it should have called `die` instead. This behavior |
78 |
* may also be triggered by a corrupt bash binary or a hardware problem |
79 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
80 |
* it appears to occur randomly, then it is likely to be triggered by a |
81 |
* hardware problem. If you suspect a hardware problem then you should try |
82 |
* some basic hardware diagnostics such as memtest. Please do not report |
83 |
* this as a bug unless it is consistently reproducible and you are sure |
84 |
* that your bash binary and hardware are functioning properly. |
85 |
/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4882: pushd: /var/tmp/portage/sys-devel/gcc-4.6.3/work/build: No such file or directory |
86 |
tar: Cowardly refusing to create an empty archive |
87 |
Try `tar --help' or `tar --usage' for more information. |
88 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device |
89 |
* |
90 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device |
91 |
* Please include /var/tmp/portage/._portage_reinstall_.y6b3sa/pym/gcc-build-logs.tar.bz2 in your bug report |
92 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/isolated-functions.sh: line 246: /var/tmp/portage/sys-devel/gcc-4.6.3/temp/logging/other: No space left on device |
93 |
* |
94 |
/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment: line 4887: popd: directory stack empty |
95 |
/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/misc-functions.sh: line 1246: /var/tmp/portage/sys-devel/gcc-4.6.3/.die_hooks: No space left on device |
96 |
Traceback (most recent call last): |
97 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 228, in <module> |
98 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
99 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main |
100 |
return ebuild_ipc.communicate(args) |
101 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/bin/ebuild-ipc.py", line 82, in communicate |
102 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
103 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/pym/portage/locks.py", line 105, in lockfile |
104 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
105 |
File "/var/tmp/portage/._portage_reinstall_.y6b3sa/pym/portage/__init__.py", line 259, in __call__ |
106 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
107 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.6.3/.ipc_lock' |
108 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
109 |
* behavior is known to be triggered by things such as failed variable |
110 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
111 |
* Normally, before exiting, bash should have displayed an error message |
112 |
* above. If bash did not produce an error message above, it's possible |
113 |
* that the ebuild has called `exit` when it should have called `die` |
114 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
115 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
116 |
* not reproducible or it appears to occur randomly, then it is likely to |
117 |
* be triggered by a hardware problem. If you suspect a hardware problem |
118 |
* then you should try some basic hardware diagnostics such as memtest. |
119 |
* Please do not report this as a bug unless it is consistently |
120 |
* reproducible and you are sure that your bash binary and hardware are |
121 |
* functioning properly. |
122 |
* Messages for package sys-libs/timezone-data-2013d: |
123 |
* You do not have TIMEZONE set in /etc/timezone. |
124 |
* Skipping auto-update of /etc/localtime. |
125 |
* Messages for package app-portage/portage-utils-0.30: |
126 |
* /etc/portage/postsync.d/q-reinitialize has been installed for convenience |
127 |
* If you wish for it to be automatically run at the end of every --sync: |
128 |
* # chmod +x /etc/portage/postsync.d/q-reinitialize |
129 |
* Normally this should only take a few seconds to run but file systems |
130 |
* such as ext3 can take a lot longer. To disable, simply do: |
131 |
* # chmod -x /etc/portage/postsync.d/q-reinitialize |
132 |
* Messages for package sys-apps/util-linux-2.22.2: |
133 |
* The agetty util now clears the terminal by default. You |
134 |
* might want to add --noclear to your /etc/inittab lines. |
135 |
* Messages for package sys-fs/e2fsprogs-1.42.7: |
136 |
* No /etc/mtab file, creating one temporarily |
137 |
* Messages for package sys-apps/less-457: |
138 |
* lesspipe offers colorization options. Run 'lesspipe -h' for info. |
139 |
* Messages for package sys-apps/coreutils-8.20: |
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-libs/glibc-2.15-r3: |
144 |
* Defaulting /etc/host.conf:multi to on |
145 |
* Generating all locales; edit /etc/locale.gen to save time/space |
146 |
* Messages for package sys-devel/gcc-4.6.3: |
147 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
148 |
* is known to be triggered by things such as failed variable assignments |
149 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
150 |
* exiting, bash should have displayed an error message above. If bash did |
151 |
* not produce an error message above, it's possible that the ebuild has |
152 |
* called `exit` when it should have called `die` instead. This behavior |
153 |
* may also be triggered by a corrupt bash binary or a hardware problem |
154 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
155 |
* it appears to occur randomly, then it is likely to be triggered by a |
156 |
* hardware problem. If you suspect a hardware problem then you should try |
157 |
* some basic hardware diagnostics such as memtest. Please do not report |
158 |
* this as a bug unless it is consistently reproducible and you are sure |
159 |
* that your bash binary and hardware are functioning properly. |
160 |
|
161 |
|
162 |
|
163 |
|
164 |
|
165 |
|
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 1235, 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 226, in build_target |
192 |
mytarget.run() |
193 |
File "modules/generic_stage_target.py", line 1295, in run |
194 |
apply(getattr(self,x)) |
195 |
File "modules/generic_stage_target.py", line 1240, 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-20131001/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.25424/log/stage1.log |