Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pietro Monteiro via Gdb <gdb@sourceware.org>
To: binutils@sourceware.org, gdb@sourceware.org
Cc: "Simon Marchi" <simon.marchi@efficios.com>
Subject: Upgrading autoconf and automake
Date: Sat, 07 Nov 2026 13:06:33 -0500	[thread overview]
Message-ID: <0618f4af-e2b7-468e-bc5c-d837fc75ac72@app.fastmail.com> (raw)

I decided to try upgrading autoconf and automake to the latest
available versions, respectively 2.73 and 1.19*. I did the upgrade for
GCC put the result in a branch on the forge
(https://forge.sourceware.org/pietro/gcc.git branch upgrade-autotools).

I also did the the upgrade for binutils-gdb tree and put it in a
branch on the forge too
(https://forge.sourceware.org/pietro/binutils-gdb.git branch
upgrade-autotools).

So far I did only some basic testing. The patch at the tip of that
branch has a changes to libiberty configure.ac that I still need to
sent for review.

One point that came up in the discussion about this upgrade in the GCC
mailinglist[1] is that binutils requires C99. So I want to make sure
we aren't regressing there.

What kind of testing should be done? Are other people able to help
here, specially for targets that don't use the GNU toolchain?

Thanks,
Pietro

* Automake 1.20 was just released. But I haven't looked into the
  release notes and I won't try to upgrade to it unless someone knows
  of good reason for it.

[1] https://inbox.sourceware.org/gcc/18b284b3-1b50-481a-a7ee-6e3e12073df0@app.fastmail.com/t/#u

                 reply	other threads:[~2026-11-07 18:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0618f4af-e2b7-468e-bc5c-d837fc75ac72@app.fastmail.com \
    --to=gdb@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=pietro@sociotechnical.xyz \
    --cc=simon.marchi@efficios.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