Tim Rice wrote: > None of that, but I did find a problem with the build environment > ... > I got the build environment fixed now.
OK. But this means I cannot trust your 6 other reports either. If you want something to be done about them, you need to redo these builds in a clean environment, with freshly unpacked sources, showing all details about cc brand and version, configure options, etc. And - please - different issues in different mails. > Builds fine Perfect! > but "make check" bombs. > .... > source='/opt/src/gnu/m4-1.4.10/tests/test-vasprintf-posix.c' > object='test-vasprintf-posix.o' libtool=no \ > DEPDIR=.deps depmode=gcc /bin/sh /opt/src/gnu/m4-1.4.10/depcomp \ > gcc -I. -I../lib -I/opt/src/gnu/m4-1.4.10/tests -I. > -I/opt/src/gnu/m4-1.4.10/tests -I.. -I/opt/src/gnu/m4-1.4.10/tests/.. > -I../lib -I/opt/src/gnu/m4-1.4.10/tests/../lib -g -O2 -c > /opt/src/gnu/m4-1.4.10/tests/test-vasprintf-posix.c > gcc: Internal compiler error: program cpp got fatal signal 11 > make[4]: *** [test-vasprintf-posix.o] Error 1 > .... This message tells you to upgrade your compiler. Indeed gcc-2.95.2 is known to have some bugs that were fixed in gcc-2.95.3. It's not worth working around this "make check" failure; just do "make install" without "make check". Bruno
