1 |
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build' |
2 |
make: *** [bootstrap-lean] Error 2 |
3 |
emake failed |
4 |
* ERROR: sys-devel/gcc-4.5.3-r1 failed (compile phase): |
5 |
* emake failed with bootstrap-lean |
6 |
* |
7 |
* Call stack: |
8 |
* ebuild.sh, line 75: Called src_compile |
9 |
* environment, line 4058: Called toolchain_src_compile |
10 |
* environment, line 4713: Called gcc_do_make |
11 |
* environment, line 2391: Called die |
12 |
* The specific snippet of code: |
13 |
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}"; |
14 |
* |
15 |
* If you need support, post the output of 'emerge --info =sys-devel/gcc-4.5.3-r1', |
16 |
* the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.5.3-r1'. |
17 |
|
18 |
bzip2: I/O or other error, bailing out. Possible reason follows. |
19 |
bzip2: No space left on device |
20 |
Input file = (stdin), output file = (stdout) |
21 |
tar: Child returned status 1 |
22 |
tar: Error is not recoverable: exiting now |
23 |
* |
24 |
* Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc-build-logs.tar.bz2 in your bug report |
25 |
* |
26 |
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/build.log'. |
27 |
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment'. |
28 |
* S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build' |
29 |
|
30 |
* Messages for package sys-libs/timezone-data-2011n: |
31 |
|
32 |
* You do not have TIMEZONE set in /etc/timezone. |
33 |
* Skipping auto-update of /etc/localtime. |
34 |
|
35 |
* Messages for package app-portage/portage-utils-0.8: |
36 |
|
37 |
* /etc/portage/postsync.d/q-reinitialize has been installed for convenience |
38 |
* If you wish for it to be automatically run at the end of every --sync: |
39 |
* # chmod +x /etc/portage/postsync.d/q-reinitialize |
40 |
* Normally this should only take a few seconds to run but file systems |
41 |
* such as ext3 can take a lot longer. To disable, simply do: |
42 |
* # chmod -x /etc/portage/postsync.d/q-reinitialize |
43 |
|
44 |
* Messages for package sys-libs/glibc-2.13-r4: |
45 |
|
46 |
* Generating all locales; edit /etc/locale.gen to save time/space |
47 |
|
48 |
* Messages for package sys-fs/udev-164-r2: |
49 |
|
50 |
* Unable to find kernel sources at /usr/src/linux |
51 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
52 |
* |
53 |
* udev-164 does not support Linux kernel before version 2.6.25! |
54 |
* For a reliable udev, use at least kernel 2.6.27 |
55 |
* |
56 |
* If after the udev update removable devices or CD/DVD drives |
57 |
* stop working, try re-emerging HAL before filling a bug report |
58 |
* |
59 |
* persistent-net does assigning fixed names to network devices. |
60 |
* If you have problems with the persistent-net rules, |
61 |
* just delete the rules file |
62 |
* rm /etc/udev/rules.d/70-persistent-net.rules |
63 |
* and then reboot. |
64 |
* |
65 |
* This may however number your devices in a different way than they are now. |
66 |
* |
67 |
* If you build an initramfs including udev, then please |
68 |
* make sure that the /sbin/udevadm binary gets included, |
69 |
* and your scripts changed to use it,as it replaces the |
70 |
* old helper apps udevinfo, udevtrigger, ... |
71 |
* |
72 |
* mount options for directory /dev are no longer |
73 |
* set in /etc/udev/udev.conf, but in /etc/fstab |
74 |
* as for other directories. |
75 |
* |
76 |
* If you use /dev/md/*, /dev/loop/* or /dev/rd/*, |
77 |
* then please migrate over to using the device names |
78 |
* /dev/md*, /dev/loop* and /dev/ram*. |
79 |
* The devfs-compat rules have been removed. |
80 |
* For reference see Bug #269359. |
81 |
* |
82 |
* Rules for /dev/hd* devices have been removed |
83 |
* Please migrate to libata. |
84 |
* |
85 |
* For more information on udev on Gentoo, writing udev rules, and |
86 |
* fixing known issues visit: |
87 |
* http://www.gentoo.org/doc/en/udev-guide.xml |
88 |
|
89 |
* Messages for package sys-libs/gdbm-1.8.3-r4: |
90 |
|
91 |
* 32bit systems might have to rebuild all gdbm databases due to |
92 |
* LFS changes in the gdbm format. You can either delete the db |
93 |
* and regenerate it from scratch, or use the converter: |
94 |
* http://bugs.gentoo.org/attachment.cgi?id=215326 |
95 |
* |
96 |
* See this comment for information on how to use it: |
97 |
* http://bugs.gentoo.org/299390#c15 |
98 |
* |
99 |
* You should be able to locate most gdbm db's on your system with: |
100 |
* find /etc /var -type f -exec file {} + | grep 'GNU dbm 1.x or ndbm database' |
101 |
* |
102 |
* You could also try using this helper script: |
103 |
* http://bugs.gentoo.org/attachment.cgi?id=222581 |
104 |
|
105 |
* Messages for package sys-apps/portage-2.1.10.41: |
106 |
|
107 |
* If you are an ebuild developer and you plan to commit ebuilds |
108 |
* with this system then please install dev-python/pycrypto or |
109 |
* enable the ssl USE flag for >=dev-lang/python-2.6 in order |
110 |
* to enable RMD160 hash support. |
111 |
* See bug #198398 for more information. |
112 |
|
113 |
* Messages for package app-misc/ca-certificates-20111025: |
114 |
|
115 |
* You should run update-ca-certificates manually after etc-update |
116 |
|
117 |
* Messages for package dev-vcs/git-1.7.3.4-r1: |
118 |
|
119 |
* These additional scripts need some dependencies: |
120 |
* git-quiltimport : dev-util/quilt |
121 |
* git-instaweb : || ( www-servers/lighttpd www-servers/apache ) |
122 |
|
123 |
* Messages for package sys-apps/coreutils-8.7: |
124 |
|
125 |
* Make sure you run 'hash -r' in your active shells. |
126 |
* You should also re-source your shell settings for LS_COLORS |
127 |
* changes, such as: source /etc/profile |
128 |
|
129 |
* Messages for package net-misc/wget-1.12-r3: |
130 |
|
131 |
* The /etc/wget/wgetrc file has been relocated to /etc/wgetrc |
132 |
|
133 |
* Messages for package sys-fs/e2fsprogs-1.41.14: |
134 |
|
135 |
* No /etc/mtab file, creating one temporarily |
136 |
|
137 |
* Messages for package sys-devel/gcc-4.5.3-r1: |
138 |
|
139 |
* ERROR: sys-devel/gcc-4.5.3-r1 failed (compile phase): |
140 |
* emake failed with bootstrap-lean |
141 |
* |
142 |
* Call stack: |
143 |
* ebuild.sh, line 75: Called src_compile |
144 |
* environment, line 4058: Called toolchain_src_compile |
145 |
* environment, line 4713: Called gcc_do_make |
146 |
* environment, line 2391: Called die |
147 |
* The specific snippet of code: |
148 |
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}"; |
149 |
* |
150 |
* If you need support, post the output of 'emerge --info =sys-devel/gcc-4.5.3-r1', |
151 |
* the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.5.3-r1'. |
152 |
* |
153 |
* Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc-build-logs.tar.bz2 in your bug report |
154 |
* |
155 |
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/build.log'. |
156 |
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment'. |
157 |
* S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build' |
158 |
* Processed 75 info files; 5 errors. |
159 |
install-info: No space left on device for /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir |
160 |
install-info: /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir: empty file |
161 |
install-info: /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir: empty file |
162 |
install-info: /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir: empty file |
163 |
install-info: /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir: empty file |
164 |
Traceback (most recent call last): |
165 |
File "/usr/bin/emerge", line 43, in <module> |
166 |
retval = emerge_main() |
167 |
File "/usr/lib/portage/pym/_emerge/main.py", line 2034, in emerge_main |
168 |
trees, mtimedb, retval) |
169 |
File "/usr/lib/portage/pym/_emerge/main.py", line 390, in post_emerge |
170 |
mtimedb.commit() |
171 |
File "/usr/lib/portage/pym/portage/util/mtimedb.py", line 82, in commit |
172 |
f.close() |
173 |
File "/usr/lib/portage/pym/portage/util/__init__.py", line 1163, in close |
174 |
f.close() |
175 |
IOError: [Errno 28] No space left on device |
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/lib64/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/lib64/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 stage3 |
199 |
Catalyst aborting.... |
200 |
lockfile does not exist '/release/buildroot/x86-dev/tmp/default/stage3-i486-20120117/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.26828/log/stage3.log |