1 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_program_options-mt-1_49.a': No space left on device |
2 |
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_random-mt-1_49.a |
3 |
|
4 |
cp "bin.v2/libs/random/build/gcc-4.5/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_random-mt-1_49.a" "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_random-mt-1_49.a" |
5 |
|
6 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_random-mt-1_49.a': No space left on device |
7 |
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_serialization-mt-1_49.a |
8 |
|
9 |
cp "bin.v2/libs/serialization/build/gcc-4.5/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_serialization-mt-1_49.a" "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_serialization-mt-1_49.a" |
10 |
|
11 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_serialization-mt-1_49.a': No space left on device |
12 |
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wserialization-mt-1_49.a |
13 |
|
14 |
cp "bin.v2/libs/serialization/build/gcc-4.5/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_wserialization-mt-1_49.a" "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wserialization-mt-1_49.a" |
15 |
|
16 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wserialization-mt-1_49.a': No space left on device |
17 |
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_signals-mt-1_49.a |
18 |
|
19 |
cp "bin.v2/libs/signals/build/gcc-4.5/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_signals-mt-1_49.a" "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_signals-mt-1_49.a" |
20 |
|
21 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_signals-mt-1_49.a': No space left on device |
22 |
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_prg_exec_monitor-mt-1_49.a |
23 |
|
24 |
cp "bin.v2/libs/test/build/gcc-4.5/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_prg_exec_monitor-mt-1_49.a" "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_prg_exec_monitor-mt-1_49.a" |
25 |
|
26 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_prg_exec_monitor-mt-1_49.a': No space left on device |
27 |
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_unit_test_framework-mt-1_49.a |
28 |
|
29 |
cp "bin.v2/libs/test/build/gcc-4.5/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_unit_test_framework-mt-1_49.a" "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_unit_test_framework-mt-1_49.a" |
30 |
|
31 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_unit_test_framework-mt-1_49.a': No space left on device |
32 |
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_timer-mt-1_49.a |
33 |
|
34 |
cp "bin.v2/libs/timer/build/gcc-4.5/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_timer-mt-1_49.a" "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_timer-mt-1_49.a" |
35 |
|
36 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_timer-mt-1_49.a': No space left on device |
37 |
common.copy /var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wave-mt-1_49.a |
38 |
|
39 |
cp "bin.v2/libs/wave/build/gcc-4.5/gentoorelease/boost.locale.icu-off/link-static/pch-off/threading-multi/libboost_wave-mt-1_49.a" "/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wave-mt-1_49.a" |
40 |
|
41 |
cp: cannot create regular file '/var/tmp/portage/dev-libs/boost-1.49.0-r2/image/usr/lib/libboost_wave-mt-1_49.a': No space left on device |
42 |
...failed updating 283 targets... |
43 |
* ERROR: dev-libs/boost-1.49.0-r2 failed (install phase): |
44 |
* Installation of Boost libraries failed |
45 |
* |
46 |
* Call stack: |
47 |
* ebuild.sh, line 93: Called src_install |
48 |
* environment, line 5304: Called installation |
49 |
* environment, line 5273: Called die |
50 |
* The specific snippet of code: |
51 |
* ${BJAM} -q -d+2 gentoorelease --user-config=user-config.jam ${OPTIONS} threading=single,multi ${LINK_OPTS} runtime-link=shared --includedir="${D}usr/include" --libdir="${D}usr/$(get_libdir)" $(use python && echo --python-buildid=${PYTHON_ABI}) install || die "Installation of Boost libraries failed"; |
52 |
* |
53 |
* If you need support, post the output of `emerge --info '=dev-libs/boost-1.49.0-r2'`, |
54 |
* the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.49.0-r2'`. |
55 |
/var/tmp/portage/._portage_reinstall_.ncm__4/bin/isolated-functions.sh: line 215: /var/tmp/portage/dev-libs/boost-1.49.0-r2/.die_hooks: No space left on device |
56 |
* The complete build log is located at '/var/tmp/portage/dev-libs/boost-1.49.0-r2/temp/build.log'. |
57 |
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/boost-1.49.0-r2/temp/environment'. |
58 |
* Working directory: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/work/boost_1_49_0' |
59 |
* S: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/work/boost_1_49_0' |
60 |
Traceback (most recent call last): |
61 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/bin/ebuild-ipc.py", line 299, in <module> |
62 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
63 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/bin/ebuild-ipc.py", line 296, in ebuild_ipc_main |
64 |
return ebuild_ipc.communicate(args) |
65 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/bin/ebuild-ipc.py", line 71, in communicate |
66 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
67 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/pym/portage/locks.py", line 103, in lockfile |
68 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
69 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/pym/portage/__init__.py", line 224, in __call__ |
70 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
71 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/.ipc_lock' |
72 |
* The ebuild phase 'install' has exited unexpectedly. This type of |
73 |
* behavior is known to be triggered by things such as failed variable |
74 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
75 |
* Normally, before exiting, bash should have displayed an error message |
76 |
* above. If bash did not produce an error message above, it's possible |
77 |
* that the ebuild has called `exit` when it should have called `die` |
78 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
79 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
80 |
* not reproducible or it appears to occur randomly, then it is likely to |
81 |
* be triggered by a hardware problem. If you suspect a hardware problem |
82 |
* then you should try some basic hardware diagnostics such as memtest. |
83 |
* Please do not report this as a bug unless it is consistently |
84 |
* reproducible and you are sure that your bash binary and hardware are |
85 |
* functioning properly. |
86 |
/var/tmp/portage/._portage_reinstall_.ncm__4/bin/misc-functions.sh: line 1262: /var/tmp/portage/dev-libs/boost-1.49.0-r2/.die_hooks: No space left on device |
87 |
Traceback (most recent call last): |
88 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/bin/ebuild-ipc.py", line 299, in <module> |
89 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
90 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/bin/ebuild-ipc.py", line 296, in ebuild_ipc_main |
91 |
return ebuild_ipc.communicate(args) |
92 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/bin/ebuild-ipc.py", line 71, in communicate |
93 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
94 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/pym/portage/locks.py", line 103, in lockfile |
95 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
96 |
File "/var/tmp/portage/._portage_reinstall_.ncm__4/pym/portage/__init__.py", line 224, in __call__ |
97 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
98 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/.ipc_lock' |
99 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
100 |
* behavior is known to be triggered by things such as failed variable |
101 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
102 |
* Normally, before exiting, bash should have displayed an error message |
103 |
* above. If bash did not produce an error message above, it's possible |
104 |
* that the ebuild has called `exit` when it should have called `die` |
105 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
106 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
107 |
* not reproducible or it appears to occur randomly, then it is likely to |
108 |
* be triggered by a hardware problem. If you suspect a hardware problem |
109 |
* then you should try some basic hardware diagnostics such as memtest. |
110 |
* Please do not report this as a bug unless it is consistently |
111 |
* reproducible and you are sure that your bash binary and hardware are |
112 |
* functioning properly. |
113 |
* Messages for package net-misc/dhcpcd-5.6.4: |
114 |
* You have installed dhcpcd with zeroconf support. |
115 |
* This means that it will always obtain an IP address even if no |
116 |
* DHCP server can be contacted, which will break any existing |
117 |
* failover support you may have configured in your net configuration. |
118 |
* This behaviour can be controlled with the -L flag. |
119 |
* See the dhcpcd man page for more details. |
120 |
* |
121 |
* Users upgrading from 4.0 series should pay attention to removal |
122 |
* of compat useflag. This changes behavior of dhcp in wide manner: |
123 |
* dhcpcd no longer sends a default ClientID for ethernet interfaces. |
124 |
* This is so we can re-use the address the kernel DHCP client found. |
125 |
* To retain the old behaviour of sending a default ClientID based on the |
126 |
* hardware address for interface, simply add the keyword clientid |
127 |
* to dhcpcd.conf or use commandline parameter -I '' |
128 |
* |
129 |
* Also, users upgrading from 4.0 series should be aware that |
130 |
* the -N, -R and -Y command line options no longer exist. |
131 |
* These are controled now by nohook options in dhcpcd.conf. |
132 |
* Messages for package sys-power/acpid-2.0.17: |
133 |
* |
134 |
* You may wish to read the Gentoo Linux Power Management Guide, |
135 |
* which can be found online at: |
136 |
* http://www.gentoo.org/doc/en/power-management-guide.xml |
137 |
* |
138 |
* Messages for package dev-libs/boost-1.49.0-r2: |
139 |
* The ebuild phase 'install' has exited unexpectedly. This type of |
140 |
* behavior is known to be triggered by things such as failed variable |
141 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
142 |
* Normally, before exiting, bash should have displayed an error message |
143 |
* above. If bash did not produce an error message above, it's possible |
144 |
* that the ebuild has called `exit` when it should have called `die` |
145 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
146 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
147 |
* not reproducible or it appears to occur randomly, then it is likely to |
148 |
* be triggered by a hardware problem. If you suspect a hardware problem |
149 |
* then you should try some basic hardware diagnostics such as memtest. |
150 |
* Please do not report this as a bug unless it is consistently |
151 |
* reproducible and you are sure that your bash binary and hardware are |
152 |
* functioning properly. |
153 |
* ERROR: dev-libs/boost-1.49.0-r2 failed (install phase): |
154 |
* Installation of Boost libraries failed |
155 |
* |
156 |
* Call stack: |
157 |
* ebuild.sh, line 93: Called src_install |
158 |
* environment, line 5304: Called installation |
159 |
* environment, line 5273: Called die |
160 |
* The specific snippet of code: |
161 |
* ${BJAM} -q -d+2 gentoorelease --user-config=user-config.jam ${OPTIONS} threading=single,multi ${LINK_OPTS} runtime-link=shared --includedir="${D}usr/include" --libdir="${D}usr/$(get_libdir)" $(use python && echo --python-buildid=${PYTHON_ABI}) install || die "Installation of Boost libraries failed"; |
162 |
* |
163 |
* If you need support, post the output of `emerge --info '=dev-libs/boost-1.49.0-r2'`, |
164 |
* the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.49.0-r2'`. |
165 |
* The complete build log is located at '/var/tmp/portage/dev-libs/boost-1.49.0-r2/temp/build.log'. |
166 |
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/boost-1.49.0-r2/temp/environment'. |
167 |
* Working directory: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/work/boost_1_49_0' |
168 |
* S: '/var/tmp/portage/dev-libs/boost-1.49.0-r2/work/boost_1_49_0' |
169 |
|
170 |
|
171 |
|
172 |
|
173 |
|
174 |
|
175 |
|
176 |
!!! catalyst: Error in attempt to build packages |
177 |
|
178 |
|
179 |
Traceback (most recent call last): |
180 |
File "modules/generic_stage_target.py", line 1389, in build_packages |
181 |
"Error in attempt to build packages",env=self.env) |
182 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, in cmd |
183 |
raise CatalystError,myexc |
184 |
CatalystError |
185 |
None |
186 |
|
187 |
!!! catalyst: livecdbuild aborting due to error. |
188 |
|
189 |
Traceback (most recent call last): |
190 |
File "/usr/lib/catalyst/catalyst", line 214, in build_target |
191 |
mytarget.run() |
192 |
File "modules/generic_stage_target.py", line 1290, in run |
193 |
apply(getattr(self,x)) |
194 |
File "modules/generic_stage_target.py", line 1394, in build_packages |
195 |
"build aborting due to error." |
196 |
CatalystError |
197 |
!!! catalyst: Error encountered during run of target livecd-stage1 |
198 |
Catalyst aborting.... |
199 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/livecd-stage1-ia64-20130108/.catalyst_lock' |
200 |
|
201 |
|
202 |
|
203 |
Full build log at /catalyst-auto.9639/log/installcd-stage1.log |