From: Alan Modra <amodra@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: GDB 12.0.90 available for testing
Date: Mon, 18 Apr 2022 11:18:59 +0930 [thread overview]
Message-ID: <YlzDi8qjVkDRkqbx@squeak.grove.modra.org> (raw)
In-Reply-To: <YlxPh8H/e3Av4elZ@adacore.com>
On Sun, Apr 17, 2022 at 10:33:59AM -0700, Joel Brobecker via Binutils wrote:
> Adding binutils@ to the list, since opcode is part of binutils.
> On Wed, Apr 13, 2022 at 06:20:24PM +0200, Jose E. Marchesi wrote:
> > > From: Luis Machado <luis.machado@arm.com>
> > > diff --git a/opcodes/Makefile.am b/opcodes/Makefile.am
> > > index afd19fa7785..681fbc07584 100644
> > > --- a/opcodes/Makefile.am
> > > +++ b/opcodes/Makefile.am
> > > @@ -124,6 +124,11 @@ TARGET32_LIBOPCODES_CFILES = \
> > > arm-dis.c \
> > > avr-dis.c \
> > > bfin-dis.c \
> > > + bpf-asm.c \
> > > + bpf-desc.c \
> > > + bpf-dis.c \
> > > + bpf-ibld.c \
> > > + bpf-opc.c \
> > > cgen-asm.c \
> > > cgen-bitset.c \
> > > cgen-dis.c \
Anything that requires 64-bit BFD support does not belong in
TARGET32_LIBOPCODES_CFILES. In fact, the whole point of
TARGET32_LIBOPCODES_CFILES was to fix --enable-targets=all breakage on
32-bit hosts without --enable-64-bit-bfd. Why would you want to put
bpf here? It's a 64-bit target!
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2022-04-18 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220320055815.2A90FA4D6C@takamaka.home>
[not found] ` <fc7354be-cd31-55b7-3f95-fc892bcb2a47@arm.com>
[not found] ` <YlW9o1IAKJ/CRk8c@adacore.com>
[not found] ` <c20304ba-7fc9-db12-5555-d413350852fd@arm.com>
[not found] ` <ffe143d3-51da-c64f-a90d-80983ccad9e4@arm.com>
[not found] ` <87pmllq7jr.fsf@oracle.com>
2022-04-17 17:33 ` Joel Brobecker
2022-04-18 1:48 ` Alan Modra [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=YlzDi8qjVkDRkqbx@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).