here is the last chunk of output i recieve gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../mono -I../../libgc/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_REENTRANT -D_REENTRANT -I/usr/include -DMONO_ASSEMBLIES=\"/usr/lib\" -DMONO_CFG_DIR=\"/etc\" -DGC_LINUX_THREADS -DMONO_USE_EXC_TABLES -D_GNU_SOURCE -D_REENTRANT -fexceptions -D_FILE_OFFSET_BITS=64 -mcpu=athlon-xp -O3 -pipe -fno-strict-aliasing -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings -c rand.c -MT rand.lo -MD -MP -MF .deps/rand.TPlo -fPIC -DPIC -o .libs/rand.lo gcc: Internal error: Segmentation fault (program cc1) Please submit a full bug report. See <URL:http://bugs.gentoo.org/> for instructions. make[4]: *** [rand.lo] Error 1 make[4]: Leaving directory `/var/tmp/portage/mono-0.30.1/work/mono-0.30.1/mono/metadata' make[3]: *** [all] Error 2 make[3]: Leaving directory `/var/tmp/portage/mono-0.30.1/work/mono-0.30.1/mono/metadata' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/mono-0.30.1/work/mono-0.30.1/mono' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/mono-0.30.1/work/mono-0.30.1' make: *** [all] Error 2 !!! ERROR: dev-dotnet/mono-0.30.1 failed. !!! Function src_compile, Line 48, Exitcode 2 !!! MONO compilation failure Reproducible: Always Steps to Reproduce: 1. emerge sync && emerge gcc 2. emerge mono 3. Actual Results: I recieve a segfault, this is gcc's fault Expected Results: finished compiling nothing to note, I am using the default make.conf on a computer that has solid hardware. This is not so much a gentoo thing, just letting you know
wow, this bug is already 3 months old and no single comment? :( Can you by any chance tell us if you still have that problem when you use your curent gcc to compile a current (>=0.91) mono version?
Okay, marking WONTFIX as there's plenty of newer mono versions out, and no reponse on this bug.