Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Tomasz Kłoczko via Gdb" <gdb@sourceware.org>
To: gdb@sourceware.org
Subject: gdb and ancient GNU autotools
Date: Sat, 24 Feb 2024 16:28:08 +0000	[thread overview]
Message-ID: <CABB28CzVqpnPM1pOeKS5epErdjALMUgYPMbSWDcOkaw272XNTQ@mail.gmail.com> (raw)

Hi,

In gdb source tree in config/override.m4 is hardcoded autoconf version

m4_if(m4_defn([m4_PACKAGE_VERSION]), [2.64],

That version has been released almost SIXTEEN YEARS AGO !!!
https://savannah.gnu.org/news/?id=5867

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.

The same situation is with binutils ang gcc.

Someone has been thinking about start update all that stuff to be able to
use the latest GNU autotools and/or start moving to cmake or meson (IMO
mesoon is better) arch/OS one by one (still living for other not migrated
archs/OSsess autotools until last arch/OS still in use will be not migrated
or abandoned)?🤔

kloczek
-- 
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH <http://lnkd.in/FXPWxH>*

             reply	other threads:[~2024-02-24 16:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 16:28 Tomasz Kłoczko via Gdb [this message]
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
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=CABB28CzVqpnPM1pOeKS5epErdjALMUgYPMbSWDcOkaw272XNTQ@mail.gmail.com \
    --to=gdb@sourceware.org \
    --cc=kloczko.tomasz@gmail.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