This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: LC_MESSAGES problem ?
- To: Paul Eggert <eggert at twinsun dot com>
- Subject: Re: LC_MESSAGES problem ?
- From: Philipp Thomas <pthomas at suse dot de>
- Date: Sat, 25 Nov 2000 19:40:42 +0100
- Cc: gcc-bugs at gcc dot gnu dot org
- References: <20001120175546.A15984@zinc.skku.ac.kr> <m38zqf2eyy.fsf@otr.mynet.cygnus.com> <20001121014722.A4539@zinc.skku.ac.kr> <m31yw61t2d.fsf@otr.mynet.cygnus.com> <20001121023209.A4560@zinc.skku.ac.kr> <200011201800.KAA01708@ruby.twinsun.com>
* Paul Eggert (eggert@twinsun.com) [20001120 19:01] on libc-alpha:
> Ah yes, GCC. GCC 2.95.2 has that problem if you configure it with the
> non-default --enable-nls option. Sorry about that. I introduced the
> problem when I added the NLS option to GCC.
--enable-nls now *is* the default for anything other then canadian cross.
> GCC ought to get fixed. That was on my to-do list a while ago, but I
> ran out of time to fix it (sorry, I have only so much volunteer time).
So
#ifdef HAVE_LC_MESSAGES
setlocale (LC_MESSAGES, "");
#endif
should be changed to unconditionally use setlocale (LC_ALL, "")? IMHO this
would require carefull review of the GCC code to see that nothing breaks
because of changing collation rules etc.
But as GCC does seem to need a fix, I can do it easily as I now maintain the
i18n specific parts of gcc.
BTW, that's also the reason why I pushed for the inclusion of your and
Martin v. Loewis patches to gettext to go into the official version ( and
because Bruno Haible is comaintainer of gettext I actually succeeded :).
> In the meantime, to work around the problem, don't specify enable-nls when
> --configuring GCC.
JFI, at least for the CVS versions of gcc you nowadays have to specify
--disable-nls to not use it.
Philipp
--
Penguins shall save the dinosaurs
-- Handelsblatt about Linux on S/390