<snip> > > I would expect to see a failure in stage 1 or stage 2 but rarely > > ever stage 3. If anyone has a clue where to look for such a > > beastly error, do let me know. Please. > > <snip> ... that the linker did not run over some sort > of resource limit, e.g., set by ulimit. > > Ian Well Sir, good guess. I incresed the stack size quite a bit : sedna $ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 127435 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 65536 cpu time (seconds, -t) unlimited max user processes (-u) 1024 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Then went back and ran the exact same configure : sedna $ ../gcc-4.7.2/configure \ > --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu \ > --with-as=/usr/local/bin/gas --with-ld=/usr/local/bin/gld --enable-multilib --enable-nls \ > --enable-threads=posix --enable-libada --enable-libssp --enable-lto \ > --enable-stage1-languages=c --enable-shared \ > --prefix=/usr/local/gcc4 --with-local-prefix=/usr/local/include > --mandir=/usr/local/gcc4/share/man --infodir=/usr/local/gcc4/share/info \ > --with-system-zlib --enable-__cxa_atexit --with-arch_32=i686 \ > --with-gmp-include=/usr/local/include --with-gmp-lib=/usr/local/lib \ > --with-mpfr-include=/usr/local/include --with-mpfr-lib=/usr/local/lib \ > --with-mpc-include=/usr/local/include --with-mpc-lib=/usr/local/lib \ > --with-pkgversion=Blastwave.org\ Inc.\ time_rfc-3339\2012-12-19\ 00\:39\:50\+00:00 \ > --enable-languages=ada,c,c++,fortran,go,objc --enable-bootstrap That went very well and the compile took a nice long time, even on a quad core opteron : real 12255.97 user 10349.35 sys 1565.99 testsuite is running now and I can only hope that things go well. Thank you for the pointer to ulimit there. Would not have guessed that and still not sure why it was an issue. Dennis
