From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: libintl: stubs or working functions
Date: Thu, 16 Apr 2015 13:33:45 -0400 [thread overview]
Message-ID: <20150416173345.GV6817@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150416171505.GA1264@euler>
On Thu, Apr 16, 2015 at 07:15:51PM +0200, Felix Janda wrote:
> As I understand applications need to pass 'need-formatstring-macros' to
> the AM_GNU_GETTEXT macro to request this functionality. But with debian
> code search I couldn't find any program doing that...
OK. AFAIK it's only GNU software like coreutils using this
functionality.
> The macro distinguishes three gettext apis. gt_api_version is 1 for the
> basic version. For the ngettext functions gt_api_version>=2 is necessary
> and for these "SYSDEP strings" gt_api_version>=3 is necessary.
>
> As I understand musl has gt_api_version=2. Is that right?
Based on your understanding of the versions, yes, that sounds right.
> To test for the api version AM_GNU_GETTEXT checks in all cases for
> bindtextdomain, gettext, _nl_msg_cat_cntr and _nl_domain_bindings. For
> gt_api_version>=2 it checks for ngettext and for gt_api_version>=3 it
> does something with __GNU_GETTEXT_SUPPORTED_REVISION we won't need to
> care about.
>
> So for musl the test gives obviously the wrong result.
>
> I guess that we don't want to export symbols _nl_*.
>
> What I would now like to ask upstream is to put the _nl_* stuff behind
> an #ifdef __GLIBC__ ...
I think we should ask why they're doing it. It sounds to me like they
should just be checking for the APIs they want to use.
Rich
next prev parent reply other threads:[~2015-04-16 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 19:18 Felix Janda
2015-04-16 0:35 ` Rich Felker
2015-04-16 1:10 ` stephen Turner
2015-04-16 17:15 ` Felix Janda
2015-04-16 17:33 ` Rich Felker [this message]
2015-05-14 16:43 ` Felix Janda
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=20150416173345.GV6817@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).