Re: Locale stuff (was Re: Cannot build gcc-3_2-branch)

[Greg Schafer <gschafer at zip dot com dot au>]

On Sat, Sep 07, 2002 at 11:09:33AM -0500, Benjamin Kosnik wrote:
> > But the configure script currently checks for the presence of the
> > "de_DE" locale. If you don't have this locale installed, then you end
> > up with "generic" as your locale model. This happened to me, hence why
> > I got bitten.
> 
> I've gotten bitten in the past with this as well. I thought I wrote up
> something about target requirements for glibc and the new locale model.
> These bits seem difficult to find though.
> 
> See the bits about "system-specific" issues under linux:
> http://gcc.gnu.org/onlinedocs/libstdc++/install.html
> 
> Improvements are welcome.

Yes, I eventually found that :-) The only trouble is, it talks primarily
about the test suite. I think some further clarification of how the actual
build is affected may be in order.

> > Or should we always be passing --enable-clocale=gnu when building?
> 
> That is an option. It forces to gnu locale, regardless of installed locales.
> 
> > What is the difference anyway? Is the ABI affected?
> 
> The difference is that named locales are supported with the gnu model.
> As this changes __c_locale, it changes the mangling, and thus the ABI.

Eek! If that is so, then maybe the situation needs to be clarified on the
ABI page:-

http://gcc.gnu.org/gcc-3.2/c++-abi.html

The page already says for GNU/Linux systems to use "GNU C Library version
2.2.5 or newer". I see no harm in also specifying  --enable-clocale=gnu
to ensure the right model is used. Otherwise some folk may accidentally
end up with ABI incompatible C++ libs.

CC'ing AJ as he seems to be resposible for that page.

Thanks for your time.
Greg