From: Sam James via Gdb <gdb@sourceware.org>
To: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>
Cc: Sam James <sam@gentoo.org>, gdb@sourceware.org
Subject: Re: gdb and ancient GNU autotools
Date: Sat, 24 Feb 2024 17:21:09 +0000 [thread overview]
Message-ID: <87o7c56ale.fsf@gentoo.org> (raw)
In-Reply-To: <CABB28CyrSKGdwA+uAx5hQ1qiz-=FPjFA3RNoJ8uBS-pJV9WAdg@mail.gmail.com>
Tomasz Kłoczko <kloczko.tomasz@gmail.com> writes:
> On Sat, 24 Feb 2024 at 16:53, Sam James <sam@gentoo.org> wrote:
> [..]
>
> > Literally NONE Linux distribution currently provides that version so in
> > case of any necessity to fix something in autoconf it is NOT POSSIBLE to
> > regenerate GNU autotools files.
> >
>
> This is wrong, per above.
>
> Did you try to make a simple experiment to clone for example gdb repo and execute "autoreconf -fiv"?
You misread what I said. I was saying that it does not need
autoconf-2.64.
>
> I've done that with autoconf 2.72, automake 1.16 and libtool 2.4.7 and here is the result:
> [...]>
> And autoconf 2.69 has been released (sic!) ONLY TWELVE years ago ..
>
Again, I actually agree with needing to move to 2.72. But you've misread
my previous message.
Also note that while autoconf-2.69 is old, it took a long time for
autoconf-2.7{0,1} to be released, so it's not quite a fair comparison.
next prev parent reply other threads:[~2024-02-24 17:23 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 [this message]
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
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=87o7c56ale.fsf@gentoo.org \
--to=gdb@sourceware.org \
--cc=kloczko.tomasz@gmail.com \
--cc=sam@gentoo.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