public inbox for
 help / color / mirror / Atom feed
From: Alan Modra <>
To: Tom de Vries <>
Subject: Re: [RFC][top-level] Add configure test-case
Date: Mon, 7 Nov 2022 22:04:44 +1030	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20221020151027.GA1300@delia.home>

On Thu, Oct 20, 2022 at 05:10:28PM +0200, Tom de Vries via Binutils wrote:
> Hi,
> As reported in reopened PR18632, recent commit 228cf97dd3c ("Merge
> from gcc project") dropped commit 69961a84c9b ("Don't build
> readline/libreadline.a, when --with-system-readline is supplied"), due to the
> patch only being applied to binutils-gdb repo, and not to gcc repo.

Sorry about that.

> I wondered if I could write a test-case that would regress because of this,
> such that we at least don't silently regress.
> I came up with a test-case named toplevel.exp, that can be run like this:

While I applaud anything that helps stop Alan making silly mistakes,
the real problem is either
a) that top-level binutils/gdb patches don't get applied to the gcc
   git repository in a timely manner, or
b) that we try to keep them in sync.

Maybe we should just give up on (b)?

Alan Modra
Australia Development Lab, IBM

  parent reply	other threads:[~2022-11-07 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 15:10 Tom de Vries
2022-10-31 15:03 ` Nick Clifton
2022-11-07 11:34 ` Alan Modra [this message]
2022-11-07 18:23   ` Joseph Myers
2022-11-08  7:12     ` Alan Modra
2023-01-14  8:51       ` Alexandre Oliva

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).