This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: ABI baselines, --enable-clocale choices, and that AC_TRY_RUN test
- From: Phil Edwards <phil at jaj dot com>
- To: libstdc++ at gcc dot gnu dot org
- Cc: aj at suse dot de
- Date: Thu, 12 Sep 2002 17:01:08 -0400
- Subject: Re: ABI baselines, --enable-clocale choices, and that AC_TRY_RUN test
- References: <20020905143954.A14230@disaster.jaj.com>
This is a brief plea for help.
On Thu, Sep 05, 2002 at 02:39:54PM -0400, I wrote:
> Turns out that my system, for some reason, is failing the check in
> GLIBCPP_ENABLE_CLOCALE:
>
> dnl Probe for locale support if no specific model is specified.
> dnl Default to "generic"
> [...]
> # Test for bugs early in glibc-2.2.x series
> if test x$enable_clocale_flag = xgnu; then
> AC_TRY_RUN([
> [...]
> ],
> [enable_clocale_flag=gnu],[enable_clocale_flag=generic],
> [enable_clocale_flag=generic])
>
> Don't know what the bug is, but if I try it manually, the executable
> segfaults. So, "generic" it is.
[...]
> (I'm trying a build now on another system that should be able to support
> --enable-clocale=gnu, if it works I'll test the baseline stuff there first.)
The build failed in the same manner: glibc 2.2.5 is installed, but this
test fails with a segfault. The german locale is installed on both systems.
Is there a particular fix in the glibc changelog that allows this test
to pass, and would allow me to use enable-clocale=gnu? With a changelog
entry to look for, I can investigate whether the glibc here should be
able to handle the test (and something else is breaking), or whether I'm
genuinely stuck with clocale=generic.
Thanks for any tips,
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002