[gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - stage3.spec

make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
 * ERROR: sys-devel/gcc-4.5.3-r1 failed (compile phase):
 *   emake failed with bootstrap-lean
 * 
 * Call stack:
 *     ebuild.sh, line   75:  Called src_compile
 *   environment, line 4058:  Called toolchain_src_compile
 *   environment, line 4713:  Called gcc_do_make
 *   environment, line 2391:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
 * 
 * If you need support, post the output of 'emerge --info =sys-devel/gcc-4.5.3-r1',
 * the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.5.3-r1'.

bzip2: I/O or other error, bailing out.  Possible reason follows.
bzip2: No space left on device
	Input file = (stdin), output file = (stdout)
tar: Child returned status 1
tar: Error is not recoverable: exiting now
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc-build-logs.tar.bz2 in your bug report
 * 
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment'.
 * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'

 * Messages for package sys-libs/timezone-data-2011n:

 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.

 * Messages for package app-portage/portage-utils-0.8:

 * /etc/portage/postsync.d/q-reinitialize has been installed for convenience
 * If you wish for it to be automatically run at the end of every --sync:
 *    # chmod +x /etc/portage/postsync.d/q-reinitialize
 * Normally this should only take a few seconds to run but file systems
 * such as ext3 can take a lot longer.  To disable, simply do:
 *    # chmod -x /etc/portage/postsync.d/q-reinitialize

 * Messages for package sys-libs/glibc-2.13-r4:

 * Generating all locales; edit /etc/locale.gen to save time/space

 * Messages for package sys-fs/udev-164-r2:

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * 
 * udev-164 does not support Linux kernel before version 2.6.25!
 * For a reliable udev, use at least kernel 2.6.27
 * 
 * If after the udev update removable devices or CD/DVD drives
 * stop working, try re-emerging HAL before filling a bug report
 * 
 * persistent-net does assigning fixed names to network devices.
 * If you have problems with the persistent-net rules,
 * just delete the rules file
 * 	rm /etc/udev/rules.d/70-persistent-net.rules
 * and then reboot.
 * 
 * This may however number your devices in a different way than they are now.
 * 
 * If you build an initramfs including udev, then please
 * make sure that the /sbin/udevadm binary gets included,
 * and your scripts changed to use it,as it replaces the
 * old helper apps udevinfo, udevtrigger, ...
 * 
 * mount options for directory /dev are no longer
 * set in /etc/udev/udev.conf, but in /etc/fstab
 * as for other directories.
 * 
 * If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
 * then please migrate over to using the device names
 * /dev/md*, /dev/loop* and /dev/ram*.
 * The devfs-compat rules have been removed.
 * For reference see Bug #269359.
 * 
 * Rules for /dev/hd* devices have been removed
 * Please migrate to libata.
 * 
 * For more information on udev on Gentoo, writing udev rules, and
 *          fixing known issues visit:
 *          http://www.gentoo.org/doc/en/udev-guide.xml

 * Messages for package sys-libs/gdbm-1.8.3-r4:

 * 32bit systems might have to rebuild all gdbm databases due to
 * LFS changes in the gdbm format.  You can either delete the db
 * and regenerate it from scratch, or use the converter:
 * http://bugs.gentoo.org/attachment.cgi?id=215326
 * 
 * See this comment for information on how to use it:
 * http://bugs.gentoo.org/299390#c15
 * 
 * You should be able to locate most gdbm db's on your system with:
 * find /etc /var -type f -exec file {} + | grep 'GNU dbm 1.x or ndbm database'
 * 
 * You could also try using this helper script:
 * http://bugs.gentoo.org/attachment.cgi?id=222581

 * Messages for package sys-apps/portage-2.1.10.41:

 * If you are an ebuild developer and you plan to commit ebuilds
 * with this system then please install dev-python/pycrypto or
 * enable the ssl USE flag for >=dev-lang/python-2.6 in order
 * to enable RMD160 hash support.
 * See bug #198398 for more information.

 * Messages for package app-misc/ca-certificates-20111025:

 * You should run update-ca-certificates manually after etc-update

 * Messages for package dev-vcs/git-1.7.3.4-r1:

 * These additional scripts need some dependencies:
 *   git-quiltimport  : dev-util/quilt
 *   git-instaweb     : || ( www-servers/lighttpd www-servers/apache )

 * Messages for package sys-apps/coreutils-8.7:

 * 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 net-misc/wget-1.12-r3:

 * The /etc/wget/wgetrc file has been relocated to /etc/wgetrc

 * Messages for package sys-fs/e2fsprogs-1.41.14:

 * No /etc/mtab file, creating one temporarily

 * Messages for package sys-devel/gcc-4.5.3-r1:

 * ERROR: sys-devel/gcc-4.5.3-r1 failed (compile phase):
 *   emake failed with bootstrap-lean
 * 
 * Call stack:
 *     ebuild.sh, line   75:  Called src_compile
 *   environment, line 4058:  Called toolchain_src_compile
 *   environment, line 4713:  Called gcc_do_make
 *   environment, line 2391:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
 * 
 * If you need support, post the output of 'emerge --info =sys-devel/gcc-4.5.3-r1',
 * the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.5.3-r1'.
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc-build-logs.tar.bz2 in your bug report
 * 
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment'.
 * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
 * Processed 75 info files; 5 errors.
install-info: No space left on device for /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir
install-info: /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir: empty file
install-info: /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir: empty file
install-info: /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir: empty file
install-info: /usr/share/binutils-data/i486-pc-linux-gnu/2.21.1/info/dir: empty file
Traceback (most recent call last):
  File "/usr/bin/emerge", line 43, in <module>
    retval = emerge_main()
  File "/usr/lib/portage/pym/_emerge/main.py", line 2034, in emerge_main
    trees, mtimedb, retval)
  File "/usr/lib/portage/pym/_emerge/main.py", line 390, in post_emerge
    mtimedb.commit()
  File "/usr/lib/portage/pym/portage/util/mtimedb.py", line 82, in commit
    f.close()
  File "/usr/lib/portage/pym/portage/util/__init__.py", line 1163, in close
    f.close()
IOError: [Errno 28] No space left on device

!!! 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/lib64/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/lib64/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 stage3
Catalyst aborting....
lockfile does not exist '/release/buildroot/x86-dev/tmp/default/stage3-i486-20120117/.catalyst_lock'



Full build log at /tmp/catalyst-auto.26828/log/stage3.log