Re: need more help compiling from CVS
- From: "Andrew S . Halper" <ashalper acm org>
- To: "Andrew S . Halper" <ashalper acm org>
- Cc: dia-list gnome org
- Subject: Re: need more help compiling from CVS
- Date: Sun, 29 Jul 2001 21:03:35 -0700
On 2001.07.29 17:12 Andrew S . Halper wrote:
On 2001.07.29 15:26 Cyrille Chepelov wrote:
This looks like the big bad NLS bug which others have been experiencing.
Let's fix it !
What is your glibc version (including devel version if there can be a
mismatch with your packaging system) ? FWIW, I've got version 2.2.3 (which
tends to disable gettext and provide its own).
My glibc is 2.2.2.
This looks suspicious:
[ashalper rocket app]$ strings /lib/libnsl-2.2.2.so | grep dcgettext
__dcgettext
dcgettext
[ashalper rocket app]$
and on line 19756 of preferences.i (i.e. the preprocessor output of
preferences.c):
message_error((__extension__ ({ char *__result; if (__builtin_constant_p
("Could not open `%s' for writing")) { static char *__translation__; static int
__catalog_counter__; if (! __translation__ || __catalog_counter__ !=
_nl_msg_cat_cntr) { __translation__ = dcgettext__ (((void *)0), "Could not open
`%s' for writing", __LC_MESSAGES); __catalog_counter__ = _nl_msg_cat_cntr; }
__result = __translation__; } else __result = dcgettext__ (((void *)0), "Could
not open `%s' for writing", __LC_MESSAGES); __result; })), filename);
It kind of looks like maybe a macro somewhere should be calling dcgettext
(prototyped in /usr/include/libintl.h) instead of dcgettext__ ?
Hope this helps,
Andy
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]