From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QTpMM-0005sx-5p for garchives@archives.gentoo.org; Tue, 07 Jun 2011 06:01:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0EE701C044; Tue, 7 Jun 2011 06:01:48 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 64B0D1C044 for ; Tue, 7 Jun 2011 06:01:48 +0000 (UTC) Received: from i2 (i2.gentoo.osuosl.org [140.211.166.190]) by smtp.gentoo.org (Postfix) with SMTP id CBA7B1B400C; Tue, 7 Jun 2011 06:01:46 +0000 (UTC) Received: by i2 (sSMTP sendmail emulation); Tue, 07 Jun 2011 06:02:02 +0000 Date: Tue, 07 Jun 2011 06:02:02 +0000 From: catalyst@dolphin.ia64.dev.gentoo.org To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage1.spec Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Release Engineering Autobuilds X-BeenThere: gentoo-releng-autobuilds@gentoo.org X-BeenThere: gentoo-releng-autobuilds@lists.gentoo.org Message-Id: <20110607060149.0EE701C044@pigeon.gentoo.org> X-Archives-Salt: X-Archives-Hash: eeb3ea0841c430c9ecdbea6980364a73 gzip -9n /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/CSN_369103 .././scripts/mkinstalldirs /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps 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 /usr/bin/install -c -m 644 charmaps/CWI /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/CWI gzip -9n /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/CWI .././scripts/mkinstalldirs /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps 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 /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 gzip -9n /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DEC-MCS .././scripts/mkinstalldirs /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps 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 /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 gzip -9n /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003 gzip: /var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003.gz: No space left on device make[2]: *** [/var/tmp/portage/sys-libs/glibc-2.11.3/image//usr/share/i18n/charmaps/DIN_66003.gz] Error 1 make[2]: Leaving directory `/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3/localedata' make[1]: *** [localedata/subdir_install] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3' make: *** [install] Error 2 emake failed * ERROR: sys-libs/glibc-2.11.3 failed (install phase): * (no error message) * * Call stack: * ebuild.sh, line 56: Called src_install * environment, line 3826: Called eblit-run 'src_install' * environment, line 1164: Called eblit-glibc-src_install * src_install.eblit, line 238: Called toolchain-glibc_src_install * src_install.eblit, line 22: Called die * The specific snippet of code: * emake install_root="${install_root}" install || die * * If you need support, post the output of 'emerge --info =sys-libs/glibc-2.11.3', * the complete build log and the output of 'emerge -pqv =sys-libs/glibc-2.11.3'. /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 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/environment'. * S: '/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3' Traceback (most recent call last): File "/usr/lib/portage/bin/ebuild-ipc.py", line 250, in sys.exit(ebuild_ipc_main(sys.argv[1:])) File "/usr/lib/portage/bin/ebuild-ipc.py", line 247, in ebuild_ipc_main return ebuild_ipc.communicate(args) File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) File "/usr/lib/portage/pym/portage/locks.py", line 72, in lockfile myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) File "/usr/lib/portage/pym/portage/__init__.py", line 226, in __call__ rval = self._func(*wrapped_args, **wrapped_kwargs) OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-libs/glibc-2.11.3/.ipc_lock' * The ebuild phase 'install' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable * assignments (bug #190128) or bad substitution errors (bug #200313). * Normally, before exiting, bash should have displayed an error message * above. If bash did not produce an error message above, it's possible * that the ebuild has called `exit` when it should have called `die` * instead. This behavior may also be triggered by a corrupt bash binary or * a hardware problem such as memory or cpu malfunction. If the problem is * not reproducible or it appears to occur randomly, then it is likely to * be triggered by a hardware problem. If you suspect a hardware problem * then you should try some basic hardware diagnostics such as memtest. * Please do not report this as a bug unless it is consistently * reproducible and you are sure that your bash binary and hardware are * functioning properly. /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 /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 * ERROR: sys-libs/glibc-2.11.3 failed: /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 * error processing environment /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 * /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 * Call stack: /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 * misc-functions.sh, line 17: Called source '/usr/lib/portage/bin/ebuild.sh' /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 * ebuild.sh, line 1951: Called die /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 * The specific snippet of code: /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 * preprocess_ebuild_env || \ /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 * die "error processing environment" /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 * /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 * If you need support, post the output of 'emerge --info =sys-libs/glibc-2.11.3', /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 * the complete build log and the output of 'emerge -pqv =sys-libs/glibc-2.11.3'. /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 /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 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/build.log'. /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 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/environment'. /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 * S: '/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3' Traceback (most recent call last): File "/usr/lib/portage/bin/ebuild-ipc.py", line 250, in sys.exit(ebuild_ipc_main(sys.argv[1:])) File "/usr/lib/portage/bin/ebuild-ipc.py", line 247, in ebuild_ipc_main return ebuild_ipc.communicate(args) File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) File "/usr/lib/portage/pym/portage/locks.py", line 72, in lockfile myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) File "/usr/lib/portage/pym/portage/__init__.py", line 226, in __call__ rval = self._func(*wrapped_args, **wrapped_kwargs) OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-libs/glibc-2.11.3/.ipc_lock' * The ebuild phase 'die_hooks' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable * assignments (bug #190128) or bad substitution errors (bug #200313). * Normally, before exiting, bash should have displayed an error message * above. If bash did not produce an error message above, it's possible * that the ebuild has called `exit` when it should have called `die` * instead. This behavior may also be triggered by a corrupt bash binary or * a hardware problem such as memory or cpu malfunction. If the problem is * not reproducible or it appears to occur randomly, then it is likely to * be triggered by a hardware problem. If you suspect a hardware problem * then you should try some basic hardware diagnostics such as memtest. * Please do not report this as a bug unless it is consistently * reproducible and you are sure that your bash binary and hardware are * functioning properly. * Messages for package sys-apps/coreutils-8.7 merged to /tmp/stage1root/: * Make sure you run 'hash -r' in your active shells. * You should also re-source your shell settings for LS_COLORS * changes, such as: source /etc/profile * Messages for package sys-libs/timezone-data-2011e merged to /tmp/stage1root/: * You do not have TIMEZONE set in /tmp/stage1root/etc/timezone. * Setting /tmp/stage1root/etc/localtime to Factory. * Messages for package net-misc/wget-1.12-r3 merged to /tmp/stage1root/: * The /etc/wget/wgetrc file has been relocated to /etc/wgetrc * Messages for package sys-libs/glibc-2.11.3 merged to /tmp/stage1root/: * The ebuild phase 'install' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable * assignments (bug #190128) or bad substitution errors (bug #200313). * Normally, before exiting, bash should have displayed an error message * above. If bash did not produce an error message above, it's possible * that the ebuild has called `exit` when it should have called `die` * instead. This behavior may also be triggered by a corrupt bash binary or * a hardware problem such as memory or cpu malfunction. If the problem is * not reproducible or it appears to occur randomly, then it is likely to * be triggered by a hardware problem. If you suspect a hardware problem * then you should try some basic hardware diagnostics such as memtest. * Please do not report this as a bug unless it is consistently * reproducible and you are sure that your bash binary and hardware are * functioning properly. * ERROR: sys-libs/glibc-2.11.3 failed (install phase): * (no error message) * * Call stack: * ebuild.sh, line 56: Called src_install * environment, line 3826: Called eblit-run 'src_install' * environment, line 1164: Called eblit-glibc-src_install * src_install.eblit, line 238: Called toolchain-glibc_src_install * src_install.eblit, line 22: Called die * The specific snippet of code: * emake install_root="${install_root}" install || die * * If you need support, post the output of 'emerge --info =sys-libs/glibc-2.11.3', * the complete build log and the output of 'emerge -pqv =sys-libs/glibc-2.11.3'. * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.11.3/temp/environment'. * S: '/var/tmp/portage/sys-libs/glibc-2.11.3/work/glibc-2.11.3' * IMPORTANT: 1 news items need reading for repository 'gentoo'. * Use eselect news to read news items. !!! catalyst: run script failed. Traceback (most recent call last): File "modules/generic_stage_target.py", line 1207, in run_local "run script failed.",env=self.env) File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd raise CatalystError,myexc CatalystError None !!! catalyst: Stage build aborting due to error. Traceback (most recent call last): File "/usr/lib/catalyst/catalyst", line 209, in build_target mytarget.run() File "modules/generic_stage_target.py", line 1263, in run apply(getattr(self,x)) File "modules/generic_stage_target.py", line 1212, in run_local raise CatalystError,"Stage build aborting due to error." CatalystError !!! catalyst: Error encountered during run of target stage1 Catalyst aborting.... lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-ia64-20110607/.catalyst_lock' Full build log at /tmp/catalyst-auto.9197/log/stage1.log