Memory faults (was Re: Problems compiling gcc-1.28)

[Lenny Tropiano]

In article <15370 at agate.BERKELEY.EDU> c60c-2av at web-2b.berkeley.edu (John Sasinowski) writes:
|>
|>I have been trying to compile gcc-1.28 on my UnixPC with the AT&T
|>c compiler.  I have been having some problems, and I was wondering if 
|>anyone can help me.
|>
|>First, the following output results from trying to make gnulib:
...
|>Fatal error in /lib/cpp
|>*** Error code 8
|>
|>All attempts to compile any of the other programs, such as genemit, results
|>in a large volume of error messages indicating too many #defines.
|>

Well this sorta looks vaguely familiar.  I've never compiled gcc, so I do
not know if it's something inherent to gcc itself and the preprocessor.  But
I would check your /usr/adm/unix.log file for NMI parity errors.  I had
this problem that everytime I tried to compile something it would die
with Status 8 (error code 8) or from /usr/include/sys/errno.h (Memory Fault).
You might even notice some core files laying around.  If the core file
timestamp corresponds with the NMI timestamp you have some bad memory.

I hope it's only a software problem for your sake...  

-Lenny
-- 
Lenny Tropiano             ICUS Software Systems         [w] +1 (516) 582-5525
lenny at icus.islp.ny.us      Telex; 154232428 ICUS         [h] +1 (516) 968-8576
{talcott,decuac,boulder,hombre,pacbell,sbcs}!icus!lenny  attmail!icus!lenny
        ICUS Software Systems -- PO Box 1; Islip Terrace, NY  11752