| 1 |
gzip -9n /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/CSN_369103 |
| 2 |
.././scripts/mkinstalldirs /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps |
| 3 |
rm -f /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/CWI /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/CWI.gz |
| 4 |
/usr/bin/install -c -m 644 charmaps/CWI /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/CWI |
| 5 |
gzip -9n /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/CWI |
| 6 |
.././scripts/mkinstalldirs /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps |
| 7 |
rm -f /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DEC-MCS /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DEC-MCS.gz |
| 8 |
/usr/bin/install -c -m 644 charmaps/DEC-MCS /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DEC-MCS |
| 9 |
gzip -9n /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DEC-MCS |
| 10 |
.././scripts/mkinstalldirs /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps |
| 11 |
rm -f /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003 /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003.gz |
| 12 |
/usr/bin/install -c -m 644 charmaps/DIN_66003 /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003 |
| 13 |
gzip -9n /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003 |
| 14 |
gzip: /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003.gz: No space left on device |
| 15 |
make[2]: *** [/var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003.gz] Error 1 |
| 16 |
make[2]: Leaving directory `/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3/localedata' |
| 17 |
make[1]: *** [localedata/subdir_install] Error 2 |
| 18 |
make[1]: Leaving directory `/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3' |
| 19 |
make: *** [install] Error 2 |
| 20 |
emake failed |
| 21 |
* ERROR: sys-libs/glibc-2.11.3 failed (install phase): |
| 22 |
* (no error message) |
| 23 |
* |
| 24 |
* Call stack: |
| 25 |
* ebuild.sh, line 56: Called src_install |
| 26 |
* environment, line 3826: Called eblit-run 'src_install' |
| 27 |
* environment, line 1164: Called eblit-glibc-src_install |
| 28 |
* src_install.eblit, line 238: Called toolchain-glibc_src_install |
| 29 |
* src_install.eblit, line 22: Called die |
| 30 |
* The specific snippet of code: |
| 31 |
* emake install_root="${install_root}" install || die |
| 32 |
* |
| 33 |
* If you need support, post the output of 'emerge --info =sys-libs/glibc-2.11.3', |
| 34 |
* the complete build log and the output of 'emerge -pqv =sys-libs/glibc-2.11.3'. |
| 35 |
/usr/lib/portage/bin/isolated-functions.sh: line 211: /var/tmp/portage/sys-libs/glibc-2.11.3/.die_hooks: No space left on device |
| 36 |
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/build.log'. |
| 37 |
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/environment'. |
| 38 |
* S: '/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3' |
| 39 |
Traceback (most recent call last): |
| 40 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 250, in <module> |
| 41 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
| 42 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 247, in ebuild_ipc_main |
| 43 |
return ebuild_ipc.communicate(args) |
| 44 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate |
| 45 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
| 46 |
File "/usr/lib/portage/pym/portage/locks.py", line 72, in lockfile |
| 47 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
| 48 |
File "/usr/lib/portage/pym/portage/__init__.py", line 226, in __call__ |
| 49 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
| 50 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-libs/glibc-2.11.3/.ipc_lock' |
| 51 |
* The ebuild phase 'install' has exited unexpectedly. This type of |
| 52 |
* behavior is known to be triggered by things such as failed variable |
| 53 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 54 |
* Normally, before exiting, bash should have displayed an error message |
| 55 |
* above. If bash did not produce an error message above, it's possible |
| 56 |
* that the ebuild has called `exit` when it should have called `die` |
| 57 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 58 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 59 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 60 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 61 |
* then you should try some basic hardware diagnostics such as memtest. |
| 62 |
* Please do not report this as a bug unless it is consistently |
| 63 |
* reproducible and you are sure that your bash binary and hardware are |
| 64 |
* functioning properly. |
| 65 |
/usr/lib/portage/bin/ebuild.sh: line 1837: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/environment.filtered: No space left on device |
| 66 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 67 |
* ERROR: sys-libs/glibc-2.11.3 failed: |
| 68 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 69 |
* error processing environment |
| 70 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 71 |
* |
| 72 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 73 |
* Call stack: |
| 74 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 75 |
* misc-functions.sh, line 17: Called source '/usr/lib/portage/bin/ebuild.sh' |
| 76 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 77 |
* ebuild.sh, line 1951: Called die |
| 78 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 79 |
* The specific snippet of code: |
| 80 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 81 |
* preprocess_ebuild_env || \ |
| 82 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 83 |
* die "error processing environment" |
| 84 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 85 |
* |
| 86 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 87 |
* If you need support, post the output of 'emerge --info =sys-libs/glibc-2.11.3', |
| 88 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 89 |
* the complete build log and the output of 'emerge -pqv =sys-libs/glibc-2.11.3'. |
| 90 |
/usr/lib/portage/bin/isolated-functions.sh: line 211: /var/tmp/portage/sys-libs/glibc-2.11.3/.die_hooks: No space left on device |
| 91 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 92 |
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/build.log'. |
| 93 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 94 |
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/environment'. |
| 95 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/glibc-2.11.3/temp/logging/other: No space left on device |
| 96 |
* S: '/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3' |
| 97 |
Traceback (most recent call last): |
| 98 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 250, in <module> |
| 99 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
| 100 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 247, in ebuild_ipc_main |
| 101 |
return ebuild_ipc.communicate(args) |
| 102 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate |
| 103 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
| 104 |
File "/usr/lib/portage/pym/portage/locks.py", line 72, in lockfile |
| 105 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
| 106 |
File "/usr/lib/portage/pym/portage/__init__.py", line 226, in __call__ |
| 107 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
| 108 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-libs/glibc-2.11.3/.ipc_lock' |
| 109 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
| 110 |
* behavior is known to be triggered by things such as failed variable |
| 111 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 112 |
* Normally, before exiting, bash should have displayed an error message |
| 113 |
* above. If bash did not produce an error message above, it's possible |
| 114 |
* that the ebuild has called `exit` when it should have called `die` |
| 115 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 116 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 117 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 118 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 119 |
* then you should try some basic hardware diagnostics such as memtest. |
| 120 |
* Please do not report this as a bug unless it is consistently |
| 121 |
* reproducible and you are sure that your bash binary and hardware are |
| 122 |
* functioning properly. |
| 123 |
|
| 124 |
* Messages for package sys-apps/coreutils-8.7 merged to /tmp/stage1root/: |
| 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 |
|
| 130 |
* Messages for package sys-libs/timezone-data-2011e merged to /tmp/stage1root/: |
| 131 |
|
| 132 |
* You do not have TIMEZONE set in /tmp/stage1root/etc/timezone. |
| 133 |
* Setting /tmp/stage1root/etc/localtime to Factory. |
| 134 |
|
| 135 |
* Messages for package net-misc/wget-1.12-r3 merged to /tmp/stage1root/: |
| 136 |
* The /etc/wget/wgetrc file has been relocated to /etc/wgetrc |
| 137 |
|
| 138 |
|
| 139 |
* Messages for package sys-libs/glibc-2.11.3 merged to /tmp/stage1root/: |
| 140 |
* The ebuild phase 'install' has exited unexpectedly. This type of |
| 141 |
* behavior is known to be triggered by things such as failed variable |
| 142 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 143 |
* Normally, before exiting, bash should have displayed an error message |
| 144 |
* above. If bash did not produce an error message above, it's possible |
| 145 |
* that the ebuild has called `exit` when it should have called `die` |
| 146 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 147 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 148 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 149 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 150 |
* then you should try some basic hardware diagnostics such as memtest. |
| 151 |
* Please do not report this as a bug unless it is consistently |
| 152 |
* reproducible and you are sure that your bash binary and hardware are |
| 153 |
* functioning properly. |
| 154 |
* ERROR: sys-libs/glibc-2.11.3 failed (install phase): |
| 155 |
* (no error message) |
| 156 |
* |
| 157 |
* Call stack: |
| 158 |
* ebuild.sh, line 56: Called src_install |
| 159 |
* environment, line 3826: Called eblit-run 'src_install' |
| 160 |
* environment, line 1164: Called eblit-glibc-src_install |
| 161 |
* src_install.eblit, line 238: Called toolchain-glibc_src_install |
| 162 |
* src_install.eblit, line 22: Called die |
| 163 |
* The specific snippet of code: |
| 164 |
* emake install_root="${install_root}" install || die |
| 165 |
* |
| 166 |
* If you need support, post the output of 'emerge --info =sys-libs/glibc-2.11.3', |
| 167 |
* the complete build log and the output of 'emerge -pqv =sys-libs/glibc-2.11.3'. |
| 168 |
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/build.log'. |
| 169 |
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/environment'. |
| 170 |
* S: '/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3' |
| 171 |
|
| 172 |
|
| 173 |
* IMPORTANT: 1 news items need reading for repository 'gentoo'. |
| 174 |
* Use eselect news to read news items. |
| 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 stage1 |
| 199 |
Catalyst aborting.... |
| 200 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-ia64-20110607/.catalyst_lock' |
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
Full build log at /tmp/catalyst-auto.9197/log/stage1.log |
Archives