From: Mike Frysinger <vapier@gentoo.org>
To: Alan Modra <amodra@gmail.com>
Cc: Luis Machado <luis.machado@linaro.org>,
Binutils <binutils@sourceware.org>, Jim Wilson <jimw@sifive.com>
Subject: Re: [RFC] RISC-V: Fix the 32-bit --enable-targets=all build breakage.
Date: Wed, 17 Nov 2021 20:29:32 -0500 [thread overview]
Message-ID: <YZWsfFNhE/H4vgrO@vapier> (raw)
In-Reply-To: <YZWmEc6q2n9ZeSDW@squeak.grove.modra.org>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On 18 Nov 2021 11:32, Alan Modra via Binutils wrote:
> On Wed, Nov 17, 2021 at 10:52:26AM -0300, Luis Machado wrote:
> > On 11/12/21 6:34 AM, Alan Modra via Binutils wrote:
> > > On Fri, Nov 12, 2021 at 04:38:08PM +0800, Nelson Chu wrote:
> > > > Hi Alan,
> > > >
> > > > I see you have a gcc patch to fix the problem of libopcodes, so should
> > > > we still need this patch to fix the --target-all on the 32-bit host
> > > > machine?
> > >
> > > No, the patch I just committed now fixed the build problem.
> > >
> >
> > Unfortunately it seems to have side effects. The bpf sim still gets built
> > for a 32-bit host, but its opcodes dependencies are no longer there,
> > resulting in undefined references:
>
> Did such a sim configuration actually work prior to my patch? If it
> did, I'm willing to move the bpf files from TARGET64_LIBOPCODES_CFILES
> to TARGET32_LIBOPCODES_CFILES.
`--host=i686-linux-gnu --enable-targets=all --enable-sim` was working
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-11-18 1:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 8:35 Nelson Chu
2021-11-12 8:38 ` Nelson Chu
2021-11-12 9:34 ` Alan Modra
2021-11-12 9:42 ` Nelson Chu
2021-12-01 9:52 ` Luis Machado
2021-12-10 10:40 ` Andrew Burgess
2021-12-10 12:36 ` Luis Machado
2021-12-10 14:57 ` Andrew Burgess
2021-12-10 15:09 ` Luis Machado
2021-12-11 3:01 ` Nelson Chu
2021-11-17 13:52 ` Luis Machado
2021-11-18 1:02 ` Alan Modra
2021-11-18 1:29 ` Mike Frysinger [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=YZWsfFNhE/H4vgrO@vapier \
--to=vapier@gentoo.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=jimw@sifive.com \
--cc=luis.machado@linaro.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).