From: "Arsen Arsenović" <arsen@aarsen.me>
To: Bruno Haible <bruno@clisp.org>
Cc: Xi Ruoyao <xry111@xry111.site>,
gcc-patches@gcc.gnu.org, Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [PATCH 0/2] Replace intl/ with out-of-tree GNU gettext
Date: Fri, 29 Sep 2023 18:21:31 +0200 [thread overview]
Message-ID: <86y1gp6j3e.fsf@aarsen.me> (raw)
In-Reply-To: <2480347.irdbgypaU6@nimes>
[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]
Bruno Haible <bruno@clisp.org> writes:
> Arsen Arsenović wrote:
>> -+The in-tree configuration requires GNU gettext v0.22.
>
> Can you change this to "... requires GNU gettext version 0.22 or newer.", please?
> I wouldn't like to give the impression that a particular release (0.22) is the
> only one that works.
> Also, some people may understand 'v' as meaning "version", but some may not.
Certainly, good idea. Thanks for the notes.
>> +Forces the gettext tree to be configured to build and use a new static
>> +libintl, overriding the system libintl.
>
> This sounds like it has no effects on the GCC tree, only on the gettext
> tree. Surely that's not the intention?
Hmm, well, it has no primary effect on the gettext tree, only the
secondary effect of 'if gettext is configured with this flag, then other
parts of the source tree use included over system gettext'.
Do you like the following?
@@ -486,7 +486,7 @@ found in a subdirectory of your GCC sources
will be built together with GCC, unless present in the system (either in
libc or as a stand-alone library).
-The in-tree configuration requires GNU gettext v0.22.
+The in-tree configuration requires GNU gettext version 0.22 or later.
@end table
@@ -2229,7 +2229,8 @@ Specifies the type of library to search
Only available if @file{gettext} is present in the source tree.
Forces the gettext tree to be configured to build and use a new static
-libintl, overriding the system libintl.
+libintl, overriding the system libintl. Results in GCC being built
+against the newly built libintl rather than the system libintl.
@item --with-catgets
If NLS is enabled, and if the host lacks @code{gettext} but has the
I'm open to better wording in the hunk 2 paragraph.
>> --with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib
>> --without-libiconv-prefix don't search for libiconv in includedir and libdir
>> --with-libiconv-type=TYPE type of library to search for (auto/static/shared)
>> + --with-libintl-prefix[=DIR] search for libintl in DIR/include and DIR/lib
>> + --without-libintl-prefix don't search for libintl in includedir and libdir
>> + --with-libintl-type=TYPE type of library to search for (auto/static/shared)
>
> It looks like an additional space in the middle of the last three lines would
> provide a better alignment for the 'configure --help' output.
Hmm, I thought that AS_HELP_STRING handles that.. These flags are
(AFAIK) from inside AM_GNU_GETTEXT, so I'm unsure on how to change this
formatting properly.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2023-09-29 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 15:00 Arsen Arsenović
2023-09-25 15:00 ` [PATCH 1/2] intl: remove, in favor of out-of-tree gettext Arsen Arsenović
2023-09-25 15:00 ` [PATCH 2/2] *: add modern gettext Arsen Arsenović
2023-09-25 17:20 ` [PATCH 0/2] Replace intl/ with out-of-tree GNU gettext Xi Ruoyao
2023-09-25 17:28 ` Arsen Arsenović
2023-09-29 11:10 ` Bruno Haible
2023-09-29 16:21 ` Arsen Arsenović [this message]
2023-09-29 16:48 ` Bruno Haible
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=86y1gp6j3e.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=bruno@clisp.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=xry111@xry111.site \
/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).