From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] Add `intl` to EMPTY_LIB_NAMES.
Date: Sat, 12 Mar 2016 10:32:06 -0500 [thread overview]
Message-ID: <20160312153206.GC9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160312120954.GA14769@nyan>
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@gmail.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
next prev parent reply other threads:[~2016-03-12 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 5:50 OGINO Masanori
2016-03-11 4:58 ` Rich Felker
2016-03-11 7:13 ` Masanori Ogino
2016-03-11 7:21 ` Masanori Ogino
2016-03-12 12:09 ` Felix Janda
2016-03-12 15:32 ` Rich Felker [this message]
2016-03-12 22:25 ` Masanori Ogino
2016-03-12 15:30 ` Rich Felker
2016-03-12 22:28 ` Masanori Ogino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160312153206.GC9349@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).