From: Joseph Myers via Gdb <gdb@sourceware.org>
To: Simon Marchi <simark@simark.ca>
Cc: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>,
"Sam James" <sam@gentoo.org>,
gdb@sourceware.org
Subject: Re: gdb and ancient GNU autotools
Date: Tue, 27 Feb 2024 17:33:09 +0000 (UTC) [thread overview]
Message-ID: <b3af4dbe-3d7-c9c8-c549-c1263e3bd0b6@redhat.com> (raw)
In-Reply-To: <892bee4f-5d11-4e5b-b3d4-3f079f7bee43@simark.ca>
On Tue, 27 Feb 2024, Simon Marchi via Gdb wrote:
> On 2/24/24 13:30, Tomasz Kłoczko via Gdb wrote:
> > Going back to the subject: someone at least started thinking about starting
> > doing something to move away from those ancient GNU autotools versions
> > (probably kicking a few as*ess on integrating properly some
> > libtool changes) or move to meson/cmake?
>
> Good news, I found a concrete of a problem that would be fixed by moving
> to a newer autoconf:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=31417#c1
>
> You can start working on patches to bump the autoconf/automake versions,
> I can help with the review.
A reminder: mixing a libtool update into an autoconf/automake update would
be a bad idea, a libtool update is likely a lot harder, since (a) the
libtool version used is very old (reportedly based on upstream commit
2c9c38d8a12eb0a2ce7fe9c3862523026c3d5622); (b) there are many local
patches, probably including some that are not present upstream; (c)
libtool commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c will need
reverting because of usage of --with-sysroot incompatible with how the
toolchain uses that option.
I did the last autoconf/automake update in GCC, but that was building very
heavily on your work on that update for binutils-gdb and would have been a
lot harder without your work to update the shared files and show the way
for the sort of changes to make to GCC-specific files.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-02-27 17:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 16:28 Tomasz Kłoczko via Gdb
2024-02-24 16:51 ` Sam James via Gdb
2024-02-24 17:15 ` Tomasz Kłoczko via Gdb
2024-02-24 17:21 ` Sam James via Gdb
2024-02-24 18:30 ` Tomasz Kłoczko via Gdb
2024-02-24 19:31 ` Mark Wielaard
2024-02-25 0:22 ` Tomasz Kłoczko via Gdb
2024-02-25 7:56 ` Mark Wielaard
2024-02-25 8:05 ` Eli Schwartz via Gdb
2024-02-25 10:40 ` Mark Wielaard
2024-02-25 21:19 ` Eli Schwartz via Gdb
2024-02-25 21:50 ` Tomasz Kłoczko via Gdb
2024-02-25 22:20 ` Andreas Schwab
2024-02-25 23:32 ` Mark Wielaard
2024-02-26 0:29 ` Tomasz Kłoczko via Gdb
2024-02-26 0:46 ` Eli Schwartz via Gdb
2024-02-26 0:55 ` Tomasz Kłoczko via Gdb
2024-02-26 11:44 ` Mark Wielaard
2024-02-26 12:13 ` Tomasz Kłoczko via Gdb
2024-02-26 0:26 ` Eli Schwartz via Gdb
2024-02-27 15:25 ` Tom Tromey
2024-02-27 16:37 ` Simon Marchi via Gdb
2024-02-27 17:33 ` Joseph Myers via Gdb [this message]
2024-02-27 17:42 ` Tom Tromey
2024-02-27 20:44 ` Tomasz Kłoczko via Gdb
2024-02-27 20:57 ` Tomasz Kłoczko via Gdb
2024-02-27 20:59 ` Sam James via Gdb
2024-02-26 0:58 ` Andrew Pinski via Gdb
2024-02-27 15:27 ` Tom Tromey
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=b3af4dbe-3d7-c9c8-c549-c1263e3bd0b6@redhat.com \
--to=gdb@sourceware.org \
--cc=josmyers@redhat.com \
--cc=kloczko.tomasz@gmail.com \
--cc=sam@gentoo.org \
--cc=simark@simark.ca \
/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