From: Pedro Alves <pedro@palves.net>
To: Luis Machado <luis.machado@arm.com>,
Alan Modra <amodra@gmail.com>,
"Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: binutils@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH, v2] Fix 32-bit build for --enable-targets=all
Date: Fri, 29 Apr 2022 17:22:53 +0100 [thread overview]
Message-ID: <41c3c273-90cd-0f31-932b-d9bfa9655e86@palves.net> (raw)
In-Reply-To: <9d9ad2f0-ce12-b701-371e-7bb9eb0356cf@arm.com>
On 2022-04-29 13:35, Luis Machado via Binutils wrote:
>
> After some investigation, it seems the bpf target is a bit of a corner case. It's within the 64-bit bfd group, so libopcodes gets built only if --enable-64-bit-bfd. Otherwise, libopcodes doesn't include bpf.
>
> The bpf sim gets built regardless of having a 32-bit bfd or 64-bit bfd, so in the case of a 32-bit build with --enable-targets=all (and no --enable-64-bit-bfd), libopcodes doesn't include bpf, causing a libsim linking failure due to missing symbols (.
>
> Things work fine for 64-bit though. I think the fix would involve not building the sim if the bpf files are not linked into libopcodes.
Can't the sim m4_include bfd64.m4 too and check enable_64_bit_bfd like opcodes, gdb, ld, etc. do?
prev parent reply other threads:[~2022-04-29 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:25 Luis Machado
2022-04-24 14:58 ` Joel Brobecker
2022-04-25 7:40 ` Luis Machado
2022-04-26 2:52 ` Alan Modra
2022-04-26 6:31 ` Luis Machado
2022-04-26 11:43 ` Alan Modra
2022-04-27 9:57 ` Pedro Alves
2022-04-27 11:25 ` Luis Machado
2022-04-26 8:07 ` Jose E. Marchesi
2022-04-26 13:22 ` Alan Modra
2022-04-29 12:35 ` Luis Machado
2022-04-29 16:22 ` Pedro Alves [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=41c3c273-90cd-0f31-932b-d9bfa9655e86@palves.net \
--to=pedro@palves.net \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=jose.marchesi@oracle.com \
--cc=luis.machado@arm.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).