egcs 971016 build problems under sco v5.0.0

[Jeffrey A Law]

  In message < 9710171946.aa19962@mip486.nscs.fast.net >you write:
  > [ cplus-dem.c in egcs-971008 ]
  > 
  > > 	stage1/xgcc -Bstage1/ -c  -DIN_GCC    -O2 -g   -DHAVE_CONFIG_H     -I. 
  > -I. -I./config cplus-dem.c
  > > xgcc: Internal compiler error: program as got fatal signal 11
  > 
  > as dies consistently on this module, a c++ demangler program.
  > Last week, I thought that this was my old 486 flaking out, but I now
  > believe this is a gcc problem, not a hardware problem on my system.
Well, there's definitely a "as" problem since it shouldn't core
dump no mater what input it was presented with.

There may also be a gcc problem which is exposing the as bug; there's
some EH stuff that I just installed that might help.  Then again, it
might not.  I don't know.  Maybe Robert can shed some light on this
problem.

  > But it has new problems:
  > 
  > It looks like the lines below in gcc/Makefile.in
I've fixed the problem.  In general it's a bad idea to have a trailing
backslash followed by an empty line -- many makes get confused about
this.

  > The next error is on tinfo.cc:
  > 
  > >	./xgcc -B./ -O1   -DIN_GCC    -O1 -g -I./include   -g1 -DIN_LIBGCC2 -D_
  > _GCC_FLOAT_NOT_NEEDED   -fPIC -I. -I. -I./config \
  > >	  -c ./cp/tinfo.cc
  > >xgcc: Internal compiler error: program as got fatal signal 11
  > 
  > Compiling with -O0 produces
  > 
  > >(EOF):undefined name: .L_T105
  > 
  > Could this problem and the one with cplus-dem.c be related to elf/coff
  > problems?
It could

  > I will be out of town next week.
  > The patches I am using (mostly by Robert Lipe) are below.
The next egcs snapshot should have the "moral equivalent" to Robert's
patches :-)

  > gmake-3.76.1 dies with

  > >Bootstrapping the compiler
  > >gmake[1]: Entering directory `/u/william/egcs-971016/gcc'
  > >gmake CC="cc" libdir=/usr/local/lib LANGUAGES="c "
  > >gmake[2]: Entering directory `/u/william/egcs-971016/gcc'
  > >cd . && autoheader
Were you building from a pure snapshot or a snapshot + diffs?

If you build from a snapshot + diffs, then its likely that you'll
need a copy of autoconf on your system.  If you build from pure
snapshots you should never need autoconf.

For reference, if you use a diff and want to make sure all the
timestamps are reasonable (to avoid needing autoconf/autoheader
bison/yacc, etc etc) you can use the following to touch all
the generated files.

touch `find egcs-$date -name configure -print`
touch egcs-$date/gcc/{cstamp-h.in,bi-parser.c,bi-parser.h,c-gperf.h,c-parse.c,c-
parse.h,cexp.c}
touch egcs-$date/gcc/cp/{parse.c,parse.h}
touch egcs-$date/gcc/objc/objc-parse.c