This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

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


> 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.

> make bootstrap can then be restarted and will finish properly.

It finishes only becuase it leaves a corrupted object.   exception.o
is toast and attempts to use it will result in punishment.

> 2.
> In /usr/local/lib/gcc-lib, it is necessary to do
> 
> ln -s i386-pc-sco3.2v5.0.4 elf
> 
> If this is not done things like crtbegin.o, etc. that live in a 
> subdirectory below can't be found.

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.


RJL


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]