Re: Grief with Dejagnu; Testing gcc 2.95.3.test4 on SCO OS5.0.4

[David Gressett <gressett at iglobal dot net>]

At 08:33 AM 2/26/2001 -0600, you wrote:
> > make[5]: Entering directory `/u7/objdir2/gcc'
> > ./xgcc -B/usr/local/i386-pc-sco3.2v5.0.4/bin/ -B./
> > -I/usr/local/i386-pc-sco3.2v5.0.4/include -O2   -DIN_GCC     -O2 -g -O2
> > -I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED    -g -O2 -I.
> > -I../../gcc-2.95.3.test4/gcc -I../../gcc-2.95.3.test4/gcc/config
> > -I../../gcc-2.95.3.test4/gcc/../include \
> >    -c -fexceptions ../../gcc-2.95.3.test4/gcc/cp/exception.cc
> > xgcc: Internal compiler error: program as got fatal signal 11
>
>While RAM bugs might be fun to chase, my money is that this is an
>assembler bug.  If you can't upgrade the whole OS, at least pick up
>tls706 from ftp://ftp.sco.com/TLS/ to get a fixed assembler.

bingo. problem solved.

>This is a hint that someone is using "-belf" to GCC ("look in a
>directory named elf".  This would be wrong; -belf is a valid flag to
>/bin/cc and not for GCC.  GCC spells that flag "-melf".  Find where this
>is coming from and fix it.  Bonus points for doing it before the 2.95.3
>release.

I ran the build from my Kermit-95 terminal emulator and saved all the 
screen output to a session log. I found no trace of -melf, -belf, or any 
other kind of elf being applied to gcc.

The only place I have yet found a -melf/-belf confusion is in the file 
ltconfig, which doesn't seem to get used - fixing it has no effect. ( the 
problem in ltconfig is that it assumes that SCO OSR5 will always use the 
SCO cc. The tcl and expect in the last dejagnu snapshot have the same 
problem in config.in, which does get used. I haven't looked at dejagnu 1.4 
yet.)