public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Bruno Haible <bruno@clisp.org>,
	Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: Ping: [PATCH v2 0/2] Replace intl/ with out-of-tree GNU gettext
Date: Sat, 28 Oct 2023 11:22:55 +0200	[thread overview]
Message-ID: <86o7gjumkz.fsf@aarsen.me> (raw)
In-Reply-To: <CA+=Sn1nVGLXo7J3ctsjcNrCiG8PSQ--iu226iHr0M4ZSRTE1ow@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]

Hi Andrew,

Andrew Pinski <pinskia@gmail.com> writes:

> One comment from me. It would be nice to update install.texi in
> gcc/doc/ to make a mention of this requirement for non-glibc hosts.

What do you think of the following:


diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index a17016cd8977..e5137f9d7a1b 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2215,6 +2215,11 @@ which lets GCC output diagnostics in languages other than American
 English.  Native Language Support is enabled by default if not doing a
 canadian cross build.  The @option{--disable-nls} option disables NLS@.
 
+Note that this functionality requires either libintl or C standard
+library that contains support for gettext (such as the GNU C Library).
+@xref{with-included-gettext,,--with-included-gettext} for more
+information on the conditions required to get gettext support.
+
 @item --with-libintl-prefix=@var{dir}
 @itemx --without-libintl-prefix
 Searches for libintl in @file{@var{dir}/include} and
@@ -2225,6 +2230,7 @@ linker handle it.
 Specifies the type of library to search for when looking for libintl.
 @var{type} can be one of @code{auto}, @code{static} or @code{shared}.
 
+@anchor{with-included-gettext}
 @item --with-included-gettext
 Only available if @file{gettext} is present in the source tree.

Thanks.
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

  reply	other threads:[~2023-10-28  9:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 13:50 Arsen Arsenović
2023-10-06 13:50 ` [PATCH v2 1/2] intl: remove, in favor of out-of-tree gettext Arsen Arsenović
2023-10-06 13:50 ` [PATCH v2 2/2] *: add modern gettext Arsen Arsenović
2023-10-06 14:50   ` Bruno Haible
2023-10-06 15:58     ` Arsen Arsenović
2023-10-15 19:38 ` Ping: [PATCH v2 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-10-26 17:32   ` Ping^2: " Arsen Arsenović
2023-10-26 18:56   ` Ping: " Andrew Pinski
2023-10-28  9:22     ` Arsen Arsenović [this message]
2023-10-28  9:52       ` Iain Sandoe
2023-10-28 10:33         ` Arsen Arsenović

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=86o7gjumkz.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=bruno@clisp.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=pinskia@gmail.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).