From: Xi Ruoyao <xry111@xry111.site>
To: "Arsen Arsenovi�0�4" <arsen@aarsen.me>, gcc-patches@gcc.gnu.org
Cc: Bruno Haible <bruno@clisp.org>, Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [PATCH 0/2] Replace intl/ with out-of-tree GNU gettext
Date: Tue, 26 Sep 2023 01:20:49 +0800 [thread overview]
Message-ID: <c5ecd018e50999cf6ea5ced308862ecb43aaa02b.camel@xry111.site> (raw)
In-Reply-To: <20230925150921.894157-1-arsen@aarsen.me>
On Mon, 2023-09-25 at 17:00 +0200, Arsen Arsenović wrote:
> Afternoon,
>
> This patch series replaces the old (early 2000s era, AFAICT) libintl
> implementation in-tree, which relies on C constructs some compilers
> (newer clang, hopefully GCC 14) refuse to compile by default with
> out-of-tree gettext, in a manner similar to GMP et al, and adds gettext
> to download_prerequisites.
I think we need to update install.texi to mention the new dependency.
And IIUC if --disable-nls is used, we can still build GCC with neither
system gettext nor in-tree gettext. Or am I wrong? (I'm asking because
we'll need to adjust Linux From Scratch [1-3] for this change if it's
applied.)
[1]:https://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-pass1.html
[2]:https://www.linuxfromscratch.org/lfs/view/development/chapter06/gcc-pass2.html
[3]:https://www.linuxfromscratch.org/lfs/view/development/chapter08/gcc.html
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-09-25 17:20 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 ` Xi Ruoyao [this message]
2023-09-25 17:28 ` [PATCH 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-09-29 11:10 ` Bruno Haible
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=c5ecd018e50999cf6ea5ced308862ecb43aaa02b.camel@xry111.site \
--to=xry111@xry111.site \
--cc=arsen@aarsen.me \
--cc=bruno@clisp.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).