This is the mail archive of the
libstdc++@sourceware.cygnus.com
mailing list for the libstdc++ project.
Re: [CVS gcc toplevel patch] v2 + v3, --enable-libstdcxx-v3
- To: Benjamin Kosnik <bkoz at cygnus dot com>
- Subject: Re: [CVS gcc toplevel patch] v2 + v3, --enable-libstdcxx-v3
- From: Jason Merrill <jason at cygnus dot com>
- Date: 05 Apr 2000 11:54:14 -0700
- Cc: libstdc++ at sourceware dot cygnus dot com
- References: <Pine.SOL.3.91.1000405112427.29500A@cse.cygnus.com>
>>>>> Benjamin Kosnik <bkoz@cygnus.com> writes:
>> Configuring with --enable-libstdcxx-v3 should change the default for
>> -fhonor-std, not just how libgcc is built; otherwise, if the user forgets
>> to specify -fhonor-std, her code won't link.
> I agree that this is preferable. I just am unsure as to how it can be done.
> I'm trying to match the behavior of --enable-new-gxx-abi, which also only
> sets flags for libgcc.a compilation instead of actually changing the
> compiler defaults.
Which is probably also a mistake.
> . . . . the only idea I have is to change decl2.c to
> int flag_honor_std = _GPP_ENABLE_NAMESPACES;
> from
> int flag_honor_std;
> And then AC_DEFINE(_GPP_ENABLE_NAMESPACES) in gcc/configure.in when
> --enable-libstdcxx-v3 is called. Hmm.
I'd prefer the less misleading "ENABLE_STD_NAMESPACE". It should
definitely not have a leading underscore.
Jason