Re: failure on OSR 5.0.X

[Robert Lipe <robertlipe at usa dot net>]

> I received this from the mailing list, which greatly pisses me off.
> The damned ORBS folks seem to have cyberjacked me, and frankly I

I can't help with that.   Sorry.

> In other news, I was trying to report failure with OSR 5.0.X as
> detailed below.

This, however, is interesting.

> > This has failed on both 5.0.2 and 5.0.4 in the same place.  

Frightening.

> > make[5]: Entering directory `/usr15/bw/gcc-2.95/gcc'
> > ./xgcc -B./ -B/usr/local/i586-pc-sco3.2v5.0.2/bin/ -I/usr/local/i586-pc-sco3.2v5.0.2/include -O2   -DIN_GCC     -O2 -g -O2 -I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED    -g -O2 -I. -I. -I./config -I./../include \
> >   -c -fexceptions ./cp/exception.cc
> > xgcc: Internal compiler error: program as got fatal signal 11
> > make[5]: *** [exception.o] Error 1

What were the exact configure and make lines issued?

Could you issue that command (cut and paste is your friend) but add "-v"
and "--save-temps" to the line?   This should give you an `exception.s'.
Then issue the 'as' command that was displayed in the '-v' output.  It
will probably look something like this:
   /usr/ccs/bin/as -b elf -Ea,XPG4PLUS,ELF -Qn -o exception.o exception.s

If the assembler drops core on that file, please send me exception.s
I'm trying to figure out if EGCS is generating nonsense or if my 5.0.5
assembler has a bug fix that your 5.0.[24] assembler doesn't.  If I can
assemble that file then that tells us your assemblers are broken.  If
I can't assemble it, then we have to figure out why EGCS is generating
different output for the two of us.

I have reports from another 5.0.4 user that this works so I'm quite
puzzled at this point...

RJL