From: Bruno Haible <bruno@clisp.org>
To: "Kévin Le Gouguec" <legouguec@adacore.com>,
"Arsen Arsenović" <arsen@aarsen.me>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org,
Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [PATCH v2 1/2] *: add modern gettext support
Date: Mon, 20 Nov 2023 22:28:33 +0100 [thread overview]
Message-ID: <5525949.MGzKGY78j4@nimes> (raw)
In-Reply-To: <86wmucp3nr.fsf@aarsen.me>
Hi Arsen,
> > 2015-08-24 "Missing parts of fixes for in-tree libiconv" (cfe101c6a82)
> ...
> Bruno, should these modifications just be restored, or do you think
> there's some preferable way to add sibling libiconv discovery? I am
> fine with either.
As libiconv does not have a 'uninstalled-config.sh.in' script like
gettext-runtime has, the simplest solution is to just restore the modifications
(i.e. upgrade to the gnulib iconv.m4 + said modifications).
Bruno
next prev parent reply other threads:[~2023-11-20 21:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 0:17 [PATCH v2 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-09-26 0:17 ` [PATCH v2 1/2] *: add modern gettext support Arsen Arsenović
2023-09-26 2:12 ` Kevin Buettner
2023-09-26 5:09 ` Tsukasa OI
2023-09-26 8:58 ` Nick Clifton
2023-09-26 13:55 ` Arsen Arsenović
2023-09-26 7:03 ` Jan Beulich
2023-09-26 7:54 ` Iain Sandoe
2023-09-26 14:44 ` Arsen Arsenović
2023-09-27 7:11 ` Jan Beulich
2023-09-27 13:06 ` Arsen Arsenović
2023-09-27 15:19 ` Nick Clifton
2023-09-27 17:43 ` Arsen Arsenović
2023-09-28 9:43 ` Nick Clifton
2023-09-29 15:58 ` Bruno Haible
2023-09-29 16:27 ` Arsen Arsenović
2023-11-20 16:42 ` Kévin Le Gouguec
2023-11-20 20:30 ` Arsen Arsenović
2023-11-20 21:28 ` Bruno Haible [this message]
2023-09-26 0:17 ` [PATCH v2 2/2] *: suppress xgettext 0.22 charset name error Arsen Arsenović
2023-09-27 15:21 ` Nick Clifton
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=5525949.MGzKGY78j4@nimes \
--to=bruno@clisp.org \
--cc=arsen@aarsen.me \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=iain@sandoe.co.uk \
--cc=legouguec@adacore.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).