Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@redhat.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org,
	 Guinevere Larsen <guinevere@redhat.com>,
	 Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] Fix 64-bit BFD detection causing build failures
Date: Fri, 14 Feb 2025 16:08:56 +0000 (GMT)	[thread overview]
Message-ID: <06eba5a3-9c2c-016f-6d89-b8286dd4fd58@redhat.com> (raw)
In-Reply-To: <Z60prW764dOg4gI7@squeak.grove.modra.org>

On Thu, 13 Feb 2025, Alan Modra wrote:

> > We have a discrepancy with 64-bit BFD handling across our component 
> > subdirectories leading to link failures such as:
> 
> Thanks for doing this.  The patch is OK for the binutils side.

 Thank you for your review.

 I had to post v2 however as I remembered that we also support explicit 
secondary targets and if we reconfigure from `--host=i386-linux-gnu' to 
`--host=i386-linux-gnu --enable-targets=riscv64-linux-gnu,all', then the 
build will fail owing to the stale value of the `bfd_cv_64_bit' cache 
variable.  And having thought about it a bit harder the same happens, 
perhaps more importantly, when switching from `--host=i386-linux-gnu 
--enable-targets=all' to `--host=i386-linux-gnu --enable-targets=all 
--enable-64-bit-bfd'.

 Therefore I have removed the variable and the check for BFD64 is now 
always run.

  Maciej


  reply	other threads:[~2025-02-14 16:15 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 [this message]
2025-02-14 11:41 ` Guinevere Larsen
2025-02-14 16:13   ` Maciej W. Rozycki

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=06eba5a3-9c2c-016f-6d89-b8286dd4fd58@redhat.com \
    --to=macro@redhat.com \
    --cc=aburgess@redhat.com \
    --cc=amodra@gmail.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