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

[Benjamin Kosnik]

> Ok, as pointed out by Jakub, it seems that --enable-clocale=generic is
> broken.

Soon fixed, apparently.

> Which begs the question, which locale model should we be using on a
> modern linux system? I would think "gnu" after reading the docs.

The default, for a truly modern linux system, is gnu. The fallback for
all is generic.

I'm encouraged that you read the docs though! Thanks.

> 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.

> 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.

-benjamin