mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Masanori Ogino <masanori.ogino@gmail.com>
To: bug-gnu-gettext@gnu.org
Cc: musl@lists.openwall.com
Subject: AM_GNU_GETTEXT without referring internal symbols?
Date: Fri, 1 Apr 2016 21:56:34 +0900	[thread overview]
Message-ID: <CAA-4+jeUF8c+Kmv0UQi0akMAtc2hmi3pC_8=nBNcsfuRcjSgNA@mail.gmail.com> (raw)

Hello,

Now AM_GNU_GETTEXT uses _nl_msg_cat_cntr and _nl_expand_alias to check
whether the implementation is compatible with GNU gettext. However,
the symbols don't appear in libintl.h so it seems that they are not
part of the public API.

Actually, musl libc implements libintl features and the score of
gettext-tools' testsuite is equal to that with the internal libintl,
using a modified AM_GNU_GETTEXT.

The musl's libintl.h even defines __USE_GNU_GETTEXT and
__GNU_GETTEXT_SUPPORTED_REVISION, but it does not imitate private
symbols.

I had checked the archive and I've found some discussions:
https://lists.gnu.org/archive/html/bug-gnu-utils/2006-03/msg00011.html
http://lists.gnu.org/archive/html/bug-gettext/2015-11/msg00015.html

So, if the goal of the macro is check if the implementation is
compatible with GNU gettext, why don't we check the public API rather
than using internal symbols? Is it possible to check if the
implementation is not one of known "broken" implementations and/or it
is really compatible?

Regards,
-- 
Masanori Ogino


             reply	other threads:[~2016-04-01 12:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 12:56 Masanori Ogino [this message]
     [not found] ` <CAA-4+jeUF8c+Kmv0UQi0akMAtc2hmi3pC_8=nBNcsfuRcjSgNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-04  2:23   ` Daiki Ueno
     [not found]     ` <m3h9fit8lg.fsf-ueno-mXXj517/zsQ@public.gmane.org>
2016-04-04  4:23       ` Masanori Ogino
     [not found]         ` <CAA-4+jcpfOXoYx1g_48M0B7punK7r2AOU7YU-V_pdQNGYcFmng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-07  2:26           ` [musl] " Daiki Ueno
2016-04-07  5:34             ` Re: [bug-gettext] " Masanori Ogino
     [not found]               ` <CAA-4+jfbUEi1bBBP7iT2_9zaxyR+XvRb00yrWsoFj7iWiN3uUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-07  5:36                 ` [musl] " Masanori Ogino
2016-05-26  6:09                 ` Daiki Ueno
2016-05-26 12:53                   ` Re: [bug-gettext] " Masanori Ogino
2016-05-26 19:36                     ` Rich Felker
     [not found]                       ` <20160526193658.GA21636-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2016-05-27  8:48                         ` [musl] " Daiki Ueno
2016-04-07  6:26               ` Re: [bug-gettext] " Rich Felker
2016-04-07  7:12                 ` Masanori Ogino
2016-04-07 10:57                   ` Szabolcs Nagy
2016-04-07 13:53                     ` Rich Felker

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='CAA-4+jeUF8c+Kmv0UQi0akMAtc2hmi3pC_8=nBNcsfuRcjSgNA@mail.gmail.com' \
    --to=masanori.ogino@gmail.com \
    --cc=bug-gnu-gettext@gnu.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).