Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Joseph Myers via Gdb <gdb@sourceware.org>
Cc: "Simon Marchi" <simark@simark.ca>,
	"Joseph Myers" <josmyers@redhat.com>,
	"Tomasz Kłoczko" <kloczko.tomasz@gmail.com>,
	"Sam James" <sam@gentoo.org>
Subject: Re: gdb and ancient GNU autotools
Date: Tue, 27 Feb 2024 10:42:30 -0700	[thread overview]
Message-ID: <875xy9vm61.fsf@tromey.com> (raw)
In-Reply-To: <b3af4dbe-3d7-c9c8-c549-c1263e3bd0b6@redhat.com> (Joseph Myers via Gdb's message of "Tue, 27 Feb 2024 17:33:09 +0000 (UTC)")

>>>>> "Joseph" == Joseph Myers via Gdb <gdb@sourceware.org> writes:

Joseph> A reminder: mixing a libtool update into an autoconf/automake update would 
Joseph> be a bad idea, a libtool update is likely a lot harder, since (a) the 
Joseph> libtool version used is very old (reportedly based on upstream commit 
Joseph> 2c9c38d8a12eb0a2ce7fe9c3862523026c3d5622)

I wonder whether we could get rid of libtool.

The host OS landscape is a lot less varied than when it was written.
Many of the problem Unix variants are dead now.  Perhaps libtool doesn't
provide all that much value.

Tom

  reply	other threads:[~2024-02-27 17:43 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
2024-02-27 17:42             ` Tom Tromey [this message]
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=875xy9vm61.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=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