This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
SCO 5.0.2 signal 11 + exceptions problem..
- To: egcs at egcs dot cygnus dot com
- Subject: SCO 5.0.2 signal 11 + exceptions problem..
- From: Rob Kramer <ilsin at singnet dot com dot sg>
- Date: Fri, 20 Aug 1999 18:22:53 +0800
- Organization: InfoLogic Pte Ltd
Hi there, (hi Robert :)
I tried building GCC 2.95 for SCO OSR v3.2 5.0.2, and got a 'fatal
signal
11 in as' somewhere along the build (while compiling 'exception.c').
This
signal seems to occur at each of my attempts to build gcc.
-----------------
make[5]: Leaving directory `/usr/rob/gnu/gcc-obj/gcc'
make[5]: Entering directory `/usr/rob/gnu/gcc-obj/gcc'
./xgcc -B./ -B/usr/local/gcc-2.95/i586-pc-sco3.2v5.0.0/bin/
-I/usr/local/gcc- 2.95/i586-pc-sco3.2v5.0.0/include -O2 -DIN_GCC
-O2
-O -I./include - g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -g -O2
-I.
- I../../gcc-2.95/gcc -I../../gcc-2.95/gcc/config
-I../../gcc-2.95/gcc/../include \
-c -fexceptions ../../gcc-2.95/gcc/cp/exception.cc
xgcc: Internal compiler error: program as got fatal signal 11
-----------------
If I restart make, it seems to build just fine. But when trying to
compile
a 'hello world' program, I get the following:
-----------------
[ildev2] /usr/rob/c++> /usr/local/gcc-2.95/bin/g++ -fexceptions test.cc
Undefined first referenced
symbol in file
exception virtual table
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(opnew.o) __check_eh_spec
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(opdel.o) __eh_alloc
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(opnew.o) exception::what(void) const
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(tinfo.o) __cp_pop_exception
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(opdel.o) exception type_info node
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(tinfo.o) terminate(void)
/usr/tmp/ccjLebPI.o __start_cp_handler
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(opdel.o) exception type_info function
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(tinfo.o) __cp_push_exception
/usr/local/gcc-2.95/lib/gcc-lib/i586-pc-
sco3.2v5.0.0/2.95/libgcc.a(opnew.o) a.out: fatal error: Symbol
referencing
errors. No output written to a.out collect2: ld returned 1 exit status
-----------------
Sigh. This looks like my build is broken because of the signal 11 in
exception.c? I'm using egcs 1.1.1 incapable of RTTI to bootstrap. Should
it have RTTI? (couldn't get egcs 1.1.1 to compile otherwise.) I believe
exceptions need RTTI to work, but I don't need exceptions to bootstrap,
or
do I?
How to get rid of signal 11? (what *is* signal 11)
Wonder if GNU as would get that signal too..
Thanks!
Rob Kramer
robk@cyberway.com.sg