[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160312153206.GC9349@brightrain.aerifal.cx>
Date: Sat, 12 Mar 2016 10:32:06 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] Add `intl` to EMPTY_LIB_NAMES.
On Sat, Mar 12, 2016 at 01:09:54PM +0100, Felix Janda wrote:
> Masanori Ogino wrote:
> > 2016-03-11 16:13 GMT+09:00 Masanori Ogino <masanori.ogino@...il.com>:
> > > From the last link:
> > >> According to the post linked from the above, the check seems to be there
> > >> to exclude incompatible implementations of gettext(), like Solaris 7 and
> > >> NetBSD:
> > >> https://lists.gnu.org/archive/html/bug-gnu-utils/2006-03/msg00011.html
> > >>
> > >> If musl's gettext implementation is compatible with GNU gettext, I guess
> > >> we could adjust the check to accept it. However, I have no idea which
> > >> symbols or macros can be used for the check. It would be helpful if
> > >> musl people could chime in and give us a hint.
> >
> > Well, is `__USE_GNU_GETTEXT` suitable for that?
>
> That depends on whether the incompatible implementations do not also
> define this macro. The NetBSD libintl.h header does not seem to do so.
> However I'm not sure about Solaris. According to the man page its
> libintl.h does define GNU_GETTEXT_SUPPORTED_REVISION but it's not clear
> whether or not __USE_GNU_GETTEXT is also defined.
>
> It can't hurt to ask on the gettext list.
__USE_* is glibc-features.h-internal machinery to communicate between
the glibc headers (and possibly, by abuse, other GNU projects'
headers) and should never be used publicly.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
