From: Bruno Haible <bruno@clisp.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
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 13:10:49 +0200 [thread overview]
Message-ID: <2480347.irdbgypaU6@nimes> (raw)
In-Reply-To: <868r8uywdl.fsf@aarsen.me>
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.
> +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?
> --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.
Bruno
next prev parent reply other threads:[~2023-09-29 11:10 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 [this message]
2023-09-29 16:21 ` Arsen Arsenović
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=2480347.irdbgypaU6@nimes \
--to=bruno@clisp.org \
--cc=arsen@aarsen.me \
--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).