This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: [gcc-3.0, libjava]: Unresolved dependency to __cxa_call_unexpected
- To: tromey at redhat dot com
- Subject: Re: [gcc-3.0, libjava]: Unresolved dependency to __cxa_call_unexpected
- From: Manfred Hollstein <manfred dot h at gmx dot net>
- Date: Wed, 20 Jun 2001 09:14:18 +0200
- CC: gcc-bugs at gcc dot gnu dot org
- References: <3B2F8A3C.6BDD6DD9@gmx.net> <874rtcs4lj.fsf@creche.redhat.com>
- Reply-To: manfred dot h at gmx dot net
Hi Tom,
Thanks for your response. I'll try out to build Java without the
awt related flag (although it used to work sometime before the
release; last time I checked was on April 7th).
Cheers, manfred.
Tom Tromey wrote:
>
> >>>>> "Manfred" == Manfred Hollstein <manfred.h@gmx.net> writes:
>
> Manfred> I was just building plain vanilla 3.0 sources when I faced
> Manfred> this problem:
>
> Manfred> --enable-java-awt=xlib,gtk
>
> FYI, this isn't really tested much, which is why it is disabled by
> default. This might be related to your problem, see below.
>
> Manfred> Everything built fine until when 'jv-convert' should be linked;
> Manfred> this failed like follows:
> Manfred> /.libs/libgcj.so: undefined reference to `__cxa_call_unexpected'
>
> Manfred> The symbol is clearly defined in
> Manfred> i686-redhat7-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.3.0.0
> Manfred> but it looks like libtool is not linking with it.
>
> Java programs by default aren't linked against libstdc++.
>
> This error means that one of the libjava files, and I'm guessing it is
> one of the AWT peer files that you enabled with --enable-java-awt, is
> using the C++ exception code and not the Java exception code. There
> is a pragma that can be used to fix this.
>
> Meanwhile, just don't use that option.
>
> Tom