public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Binutils <binutils@sourceware.org>
Subject: Maintainer mode: wrong gettext version?
Date: Thu, 8 Sep 2022 13:04:27 +0900	[thread overview]
Message-ID: <0b894a3c-ca28-ae05-d996-9b6a7ce94d79@irq.a4lg.com> (raw)

Hello all (especially maintainers),

I was testing the maintainer mode to dig down build pipeline on
Binutils/GDB and found something strange.

According to README-maintainer-mode, enabling maintainer mode requires
following versions:

-   autoconf 2.69
-   automake 1.15.1
-   libtool 2.2.6
-   gettext 0.14.5

I tried to use the maintainer mode with Ubuntu 22.04.1 LTS (default
toolchain) with "/opt/maint-mode" to install older versions of the
software above.

Autoconf, Automake and Libtool were fine.  But I don't think Gettext
0.14.5 is the correct version.  Here's some proofs:

-   On "intl" and "libiberty", "aclocal.m4" does not have a macro
   "AC_ISC_POSIX" which is required by gettext < 0.15.
    If the build files are really built with gettext 0.14.5,
    files "{libiberty,intl}/{configure,aclocal.m4}" must have some
    traces of "AC_ISC_POSIX" but there's none in the master branch.
    That indicates that the true version of gettext is >= 0.15.
-   On gettext < 0.16, rebuilding the message files fail because
    msgfmt cannot parse lines starting with "#~|" (this syntax got
    acceptable since gettext >= 0.16).
    That suggests that the true version of gettext is >= 0.16.

And the following fact narrows the possibility even further:

-   On gettext >= 0.17, regenerated "gnulib/{aclocal.m4,configure}"
    result in different files (macros including "AM_PO_SUBDIRS" are
    copied to "gnulib/aclocal.m4").

Unless I miss something, I must conclude that the correct version of
gettext is either:

-   0.16
-   0.16.1

note: this assumes that we have consistent gettext version when...
-   regenerating ALL the build files and
-   building with the maintainer mode

Did I miss something?  Or do we need to change README-maintainer-mode to
update the version of gettext?

Thanks,
Tsukasa

             reply	other threads:[~2022-09-08  4:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  4:04 Tsukasa OI [this message]
2022-09-08  7:21 ` Andreas Schwab
2022-09-08  7:24   ` Andreas Schwab
2022-09-08  9:05 ` 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=0b894a3c-ca28-ae05-d996-9b6a7ce94d79@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.org \
    /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).