This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: libtool, java woes
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: libtool, java woes
- From: Tom Tromey <tromey at redhat dot com>
- Date: 10 Apr 2001 19:03:20 -0600
- Cc: aoliva at redhat dot com, jsturm at one-point dot com, java at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- References: <ork84uvuf3.fsf@guarana.lsd.ic.unicamp.br> <20010410121203K.mitchell@codesourcery.com>
- Reply-To: tromey at redhat dot com
>>>>> "Mark" == Mark Mitchell <mark@codesourcery.com> writes:
Alexandre> What I don't understand is why libgcj is linked with
Alexandre> libsupc++, and not with libstdc++.
Tom> We don't need or want libstdc++.
Mark> I think it's basically wrong to link with libsupc++ on any
Mark> non-embedded system. In the same way that we don't provide a
Mark> separate malloc-and-free-but-not-popen C library, we shouldn't
Mark> provide a separate new-and-delete-but-not-iostream C++ library.
I don't think this analogy holds too well. For one thing, in libjava
we don't want or need the C++ `new' support either. We just want the
exception handling code. The compiler generates calls to this code
without real user knowledge. I see this as more akin to something
like libgcc than, say, libc.
Adding libstdc++ to every Java program is a cost we would rather not
pay.
Tom