Signal 11 building 19990623 on Linux 2.2.5

[Jeffrey A Law]

  In message < 1.5.4.32.19990702121931.006bcd8c@mail.soup.dk >you write:
  > >  > I type make bootstrap.
  > >  > The process starts, but invariably ends in the /opt/egcsbuild/gcc dire
  > ctory
  > >  > :
  > >  > echo "int xxy_us_dummy;" >tmp-dum.c
  > >  > ./xgcc -B./ -B/opt/egcsoutput/i686-pc-linux-gnu/bin
  > >  > -I/opt/egcsoutput/i686-pc-linux/gnu/include -S tmp-dum.c
  > >  > xgcc: Internal compiler error: program cpp got fatal signal 11
  > >This would tend to indicate that whatever compiler you used to build egcs
  > >mis-compiled cpp.
  > >
  > >
  > >Running gdb on "cpp" might tell you something useful.
  > 
  > OK, I tried building with a precompiled egcs rather than gcc, same result.
  > GDB tells me this, looking at the core from cpp:
  > 
  > Program terminated with signal 11, Segmentation fault.
  > Reading symbols from /lib/libc.so.6...done.
  > Reading symbols from /lib/ld-linux.so.2...done.
  > #0  0x4006aa70 in _IO_new_fclose (fp=0x80647f0) at iofclose.c:45
  > iofclose.c:45: No such file or directory.
  > Breakpoint 1 at 0x4003a532: file exit.c, line 40.
  > Breakpoint 2 at 0x8059f2f: file ../../egcs/gcc/cccp.c, line 10634.
  > Breakpoint 3 at 0x40039397: file ../sysdeps/generic/abort.c, line 55.     
  > 
  > I must admit to not knowing that much about Linux, so I'm not sure what to
  > about this - I am mainly undertaking this to get gcj running at some point,
  > being rather more into java.
Let me guess, you're running glibc-2.1?  This looks a lot like some of the
failures I saw with glibc-2.1.  In fact, it was stuff like this that caused
me to back off to glibc-2.0.7.

You're core dumping inside the glibc library.  That generally indicates
a problem in the library itself.

jeff