make: *** [bootstrap] Error 2

make: *** [bootstrap] Error 2

[Ralph Schunk]

Hi everyone.
I tried compiling the lates GCC-Sources (CVS).
I get the following error and do not even understand what it's mean.


Any feedback would be appreciated.

checking for cstdio to use... stdio
checking for clocale to use... generic
checking for ISO C99 support in <math.h>... no
checking for ISO C99 support in <stdio.h>... no
checking for lldiv_t declaration... no
checking for ISO C99 support in <stdlib.h>... no
checking for additional ISO C99 support in <wchar.h>... no
checking for enabled ISO C99 support... no
checking for enabled long long I/O support... no
checking for c header strategy to use... c_std
checking for thread model used by GCC...
/home/opal/schunk/Src/GCC/gcc/libstdc++-v3/configure: test: !=: unary 
operator expected
checking for exception model to use... configure: error: unable to 
detect exception model
make[1]: *** [configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory `/home/opal/schunk/Src/GCC/GCC-obj'
make: *** [bootstrap] Error 2




-- 
Ralph Oliver Schunk
Institut für Physikalische Biologie
Heinrich-Heine Universität Duesseldorf
http://www.biophys.uni-duesseldorf.de

RE: make: *** [bootstrap] Error 2

[Rupert Wood]

Ralph Schunk wrote:

> I tried compiling the lates GCC-Sources (CVS).
> I get the following error and do not even understand what it's mean.
:
> checking for exception model to use... configure: error: unable to 
> detect exception model

This is the important line, and I'm not sure how I can phrase it much
differently: the C++ library needs to know which method of exception
handling matches your cpu and operating system's Application Binary
Interface (ABI) and either it cannot detect the ABI's scheme or the
ABI's scheme is unsupported.

You can either force SJLJ execptions with --enable-sjlj-exceptions or
build a C-only compiler with --enable-langugaes=c. You may also be able
to build objective C and Ada but you can't build C++ without an
exception scheme and GCC's java support requires C++.

I'm not sure what the implications of SJLJ exceptions are; if you don't
need to interoperate with anyone else's (including the OS's) C++
libraries then there should be no problem just picking a scheme. I
recall that there were some problems with SJLJ exceptions back in the
days of GCC 2.95.x but I imagine they've been fixed by now.

Good luck,
Rup.