public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: Nick Clifton <nickc@redhat.com>, Binutils <binutils@sourceware.org>
Subject: Re: [PATCH v2 1/2] *: add modern gettext support
Date: Tue, 26 Sep 2023 15:55:28 +0200	[thread overview]
Message-ID: <86ediluh7r.fsf@aarsen.me> (raw)
In-Reply-To: <0e53cbd9-d430-4c29-8fcd-638613f013d9@irq.a4lg.com>

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


Tsukasa OI <research_trasio@irq.a4lg.com> writes:

> Hi,
>
> While not mandatory, I recommend that checking that the maintainer mode
> works if you update gettext to 0.22.2 and update the
> README-maintainer-mode file if it does.
>
> Nick, if modern gettext should (and can) be supported, is updating the
> base maintainer mode gettext package to 0.22.2 (or something relatively
> decent) okay?

This change only affects the runtime library, so it should not impact
maintainer-mode.

I haven't tested maintainer mode thoroughly, because my system has
(patched) Autoconf 2.71, and getting Autoconf 2.69 et al can be
finnicky, but I do recall running a build with --enable-maintainer-mode,
which had .pot files get rebuilt just fine using my usual gettext
install.

The change in this patchset should effectively just replace intl/ with
gettext-runtime from 'gettext/' in the source tree, if provided, failing
back to searching the system via AM_GNU_GETTEXT otherwise.

Note that gettext-runtime also first tries probing the system unless
--with-included-gettext is provided.


I've just reconfigured and rebuilt binutils and GDB with maintainer mode
enabled, and it seems that .pot files got rebuilt as expected, as well
as some config.h.in files.  It seems that I forgot to run autoheader.
Building that copy on FreeBSD also seems to result in no issues.

Is there anything specific I should check for when looking at maintainer
mode?

Have a lovely day!
-- 
Arsen Arsenović

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

  parent reply	other threads:[~2023-09-26 14:44 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ć [this message]
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
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=86ediluh7r.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=research_trasio@irq.a4lg.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).