On Thu, 1 Nov 2007, Bruno Haible wrote: > 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.
Actually you can trust the other 6 reports. This one was a unique case. My UnixWare 7.1.4 box also has LKP (Linux Kernel Personality). Unfotunatly because I used symbolic links instead of local mount for my common source tree, the system saw that /opt/src/gnu/m4-1.4.10/configure as being in the UnixWare space and invoked the UnixWare /bin/sh instead of the Linux /bin/sh causing the problem. :-( All the other reports were on machines running native OS. > > > Builds fine > > Perfect! > > > 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". Agreed. -- Tim Rice Multitalents (707) 887-1469 [EMAIL PROTECTED]
