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]
Other format: [Raw text]

Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility


Matthias Klose <doko@cs.tu-berlin.de> writes:

> On # Sat, 3 Aug 2002 09:55:42 -0700, H. J. Lu wrote:
>> On Sat, Aug 03, 2002 at 12:49:42PM -0400, Jakub Jelinek wrote:
>> > On Sat, Aug 03, 2002 at 09:46:57AM -0700, H. J. Lu wrote:
>> > > > This begs for the question whether if libstdc++ configured with
>> > > > --enable-threads=posix and configured without this are not
>> > > > binary compatible, we shouldn't default to
>> > >			 ^^^^^^^^^^^^^^^^^
>> > > Are you suggesting the current default for Linux is a good thing and
>> > > all Linux distributions should do same?
>> > 
>> > Nope, I'm suggesting
>> > --enable-threads=posix --enable-shared --enable-__cxa_atexit
>> > to be the default for linux native (or linux targets including cross?).
>
> Agreed. How do other options affect compatibility?

Let's rearrange the flags first:

>         --with-system-zlib (affects Java only)

This one should not affect compatibility if your zlib is recent
enough (has all the needed interfaces).

>         --enable-nls
>         --without-included-gettext

These two are used to output GCC's error and warning messages in
different languages, they should not affect anything.


>         --enable-long-long
>         --enable-clocale=gnu
>         --enable-c-mbchar

These are the interesting ones ;-)

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj


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