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

(pod2man --center="GNU" --release="gcc-4.5.3" --section=7 gpl.pod > doc/gpl.7.T$$ && \
	mv -f doc/gpl.7.T$$ doc/gpl.7) || \
	(rm -f doc/gpl.7.T$$ && exit 1)
cp doc/gcc.1 doc/g++.1
perl /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/gcc/../contrib/texi2pod.pl -DBUGURL="@uref{http://bugs.gentoo.org/}" \
  < /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/gcc/fortran/invoke.texi > gfortran.pod
echo timestamp > doc/gfortran.1
(pod2man --center="GNU" --release="gcc-4.5.3" --section=1 gfortran.pod > doc/gfortran.1.T$$ && \
	mv -f doc/gfortran.1.T$$ doc/gfortran.1) || \
	(rm -f doc/gfortran.1.T$$ && exit 1)
rm gcc.pod gfortran.pod
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/gcc'
mkdir -p -- i486-pc-linux-gnu/libgcc
Checking multilib configuration for libgcc...
Configuring stage 2 in i486-pc-linux-gnu/libgcc
configure: creating cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking build system type... i486-pc-linux-gnu
checking host system type... i486-pc-linux-gnu
checking for i486-pc-linux-gnu-ar... /usr/i486-pc-linux-gnu/bin/ar
checking for i486-pc-linux-gnu-lipo... lipo
checking for i486-pc-linux-gnu-nm... /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/nm
checking for i486-pc-linux-gnu-ranlib... /usr/i486-pc-linux-gnu/bin/ranlib
checking for i486-pc-linux-gnu-strip... /usr/i486-pc-linux-gnu/bin/strip
checking whether ln -s works... yes
checking for i486-pc-linux-gnu-gcc... /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/ -B/usr/i486-pc-linux-gnu/bin/ -B/usr/i486-pc-linux-gnu/lib/ -isystem /usr/i486-pc-linux-gnu/include -isystem /usr/i486-pc-linux-gnu/sys-include   
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/ -B/usr/i486-pc-linux-gnu/bin/ -B/usr/i486-pc-linux-gnu/lib/ -isystem /usr/i486-pc-linux-gnu/include -isystem /usr/i486-pc-linux-gnu/sys-include    accepts -g... yes
checking for /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/ -B/usr/i486-pc-linux-gnu/bin/ -B/usr/i486-pc-linux-gnu/lib/ -isystem /usr/i486-pc-linux-gnu/include -isystem /usr/i486-pc-linux-gnu/sys-include    option to accept ISO C89... none needed
checking how to run the C preprocessor... /lib/cpp
checking whether decimal floating point is supported... yes
checking whether fixed-point is supported... no
checking for __attribute__((visibility("hidden")))... yes
checking whether the target assembler supports thread-local storage... yes
checking whether the thread-local storage support is from emutls... no
configure: updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: executing default commands
rm: cannot remove `./conf1hecYC/subs.awk': Bad file descriptor
rm: cannot remove `./conf1hecYC/subs1.awk': Bad file descriptor
make[3]: Entering directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/i486-pc-linux-gnu/libgcc'
# If this is the top-level multilib, build all the other
# multilibs.
/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/ -B/usr/i486-pc-linux-gnu/bin/ -B/usr/i486-pc-linux-gnu/lib/ -isystem /usr/i486-pc-linux-gnu/include -isystem /usr/i486-pc-linux-gnu/sys-include    -g -O2 -march=i486 -pipe -O2  -g -O2 -march=i486 -pipe -DIN_GCC   -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED    -I. -I. -I../.././gcc -I/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libgcc -I/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libgcc/. -I/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libgcc/../gcc -I/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libgcc/../include -I/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS  -DUSE_TLS -o _muldi3.o -MT _muldi3.o -MD -MP
  -MF _muldi3.dep -DL_muldi3 -c /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libgcc/../gcc/libgcc2.c \
  -fvisibility=hidden -DHIDE_EXPORTS
In file included from /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libgcc/../gcc/tsystem.h:105:0,
                 from /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libgcc/../gcc/libgcc2.c:29:
/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/include-fixed/limits.h:34:23: fatal error: syslimits.h: No such file or directory
compilation terminated.
make[3]: *** [_muldi3.o] Error 1
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/i486-pc-linux-gnu/libgcc'
make[2]: *** [all-stage2-target-libgcc] Error 2
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
 * ERROR: sys-devel/gcc-4.5.3-r2 failed (compile phase):
 *   emake failed with bootstrap-lean
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_compile
 *   environment, line 4043:  Called toolchain_src_compile
 *   environment, line 4683:  Called gcc_do_make
 *   environment, line 2373:  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-r2'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.5.3-r2'`.
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r2/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-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
[Errno 2] No such file or directory: '/proc/23435/fd':
   /usr/bin/sandbox "/usr/lib/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
  File "/usr/lib/portage/pym/portage/process.py", line 264, in spawn
    env, gid, groups, uid, umask, pre_exec)
  File "/usr/lib/portage/pym/portage/process.py", line 386, in _exec
    _setup_pipes(fd_pipes)
  File "/usr/lib/portage/pym/portage/process.py", line 430, in _setup_pipes
    for fd in get_open_fds():
  File "/usr/lib/portage/pym/portage/process.py", line 35, in get_open_fds
    return (int(fd) for fd in os.listdir("/proc/%i/fd" % os.getpid()) \
  File "/usr/lib/portage/pym/portage/__init__.py", line 230, in __call__
    rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory: '/proc/23435/fd'
 * 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-libs/timezone-data-2012c:
 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.
 * Messages for package app-portage/portage-utils-0.10:
 * /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-apps/baselayout-2.1-r1:
 * You should reboot the system now to get /run mounted with tmpfs!
 * Messages for package sys-libs/glibc-2.15-r2:
 * Generating all locales; edit /etc/locale.gen to save time/space
 * 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/util-linux-2.20.1-r2:
 * The agetty util now clears the terminal by default.  You
 * might want to add --noclear to your /etc/inittab lines.
 * Messages for package sys-devel/gcc-4.5.3-r2:
 * ERROR: sys-devel/gcc-4.5.3-r2 failed (compile phase):
 *   emake failed with bootstrap-lean
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_compile
 *   environment, line 4043:  Called toolchain_src_compile
 *   environment, line 4683:  Called gcc_do_make
 *   environment, line 2373:  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-r2'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.5.3-r2'`.
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r2/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-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'















!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1194, 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 206, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1254, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1199, 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-20120828/.catalyst_lock'



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