public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Mark Wielaard <mark@klomp.org>,
	builder@sourceware.org, "Maciej W. Rozycki" <macro@redhat.com>
Cc: binutils@sourceware.org, gdb-testers@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb-autoregen - failed 'git diff ...' (failure) (master)
Date: Fri, 14 Jun 2024 12:51:51 +0100	[thread overview]
Message-ID: <7808efcd-0c3e-42f3-83ba-869eeefe2e93@redhat.com> (raw)
In-Reply-To: <dcb6b903bc7da3b3fcf6136e8602d7ed922c9023.camel@klomp.org>

Hi Mark,

> It looks like not all autotool files were correctly regenerated.

Doh!

> I think the autoregen bot is right, DEFAULT_LD_ROSEGMENT should sort
> before DEFAULT_LD_TEXTREL_CHECK.

OK.

> Here I am not completely clear what happened. Did you use different
> autoconf version?

I hope not. (I used autoconf 2.69, which I hope is the correct version).

Anyway I have checked in a patch to regenerate those files, so I hope that this time it work.

Cheers
   Nick



  reply	other threads:[~2024-06-14 11:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 14:18 builder
2024-06-13 16:34 ` Mark Wielaard
2024-06-14 11:51   ` Nick Clifton [this message]
2024-06-14 12:14     ` Mark Wielaard
  -- strict thread matches above, loose matches on Subject: below --
2024-06-20  9:44 builder
2024-06-14  9:31 builder
2024-06-09 23:18 builder
2024-03-11 17:03 builder
2024-01-16  3:24 builder
2024-01-15 22:57 builder
2024-01-15 18:05 builder
2024-01-15 14:13 builder
2024-01-15 14:11 builder
2024-01-15 14:10 builder
2024-01-12 22:50 builder
2024-01-11  2:29 builder
2024-01-07  5:24 builder
2024-01-07 17:29 ` Mark Wielaard
2024-01-08  0:24   ` Alan Modra
2024-01-08 21:51     ` Mark Wielaard
2024-01-08 23:28       ` Alan Modra
2024-01-05 15:01 builder
2024-01-05 10:25 builder
2024-01-04 13:35 builder

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=7808efcd-0c3e-42f3-83ba-869eeefe2e93@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=builder@sourceware.org \
    --cc=gdb-testers@sourceware.org \
    --cc=macro@redhat.com \
    --cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).