From: "Maciej W. Rozycki" <macro@redhat.com>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org,
Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] Fix 64-bit BFD detection causing build failures
Date: Fri, 14 Feb 2025 16:13:14 +0000 (GMT) [thread overview]
Message-ID: <9cb44f25-ccf3-0f7a-fa1e-c98cfbbf964d@redhat.com> (raw)
In-Reply-To: <7e1966ec-417b-4e2d-9478-06d1ad11ad4a@redhat.com>
On Fri, 14 Feb 2025, Guinevere Larsen wrote:
> As I said in my other email, I'm not confident enough in autotools to properly
> review, but I have tested and it solves the build issue in the mips machine I
> first ran into, so feel free to add my test tag
Thank you for running this verification. Please note that I had to post
v2 now, as I realised a flaw in the use of a cache variable here. I have
carried your verification tag across though as the failure scenario is not
one you tested.
Maciej
prev parent reply other threads:[~2025-02-14 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 18:36 Maciej W. Rozycki
2025-02-12 23:07 ` Alan Modra
2025-02-14 16:08 ` Maciej W. Rozycki
2025-02-14 11:41 ` Guinevere Larsen
2025-02-14 16:13 ` Maciej W. Rozycki [this message]
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=9cb44f25-ccf3-0f7a-fa1e-c98cfbbf964d@redhat.com \
--to=macro@redhat.com \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.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