From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC PATCH 6/8] rust: Mitigate duplicate sections on matching architectures
Date: Mon, 28 Feb 2022 09:21:09 +0100 [thread overview]
Message-ID: <CANNYZj_21ZYm1vz33FbbmVZ5md-GaQEVpvbrtCNkbh5Ck-0snQ@mail.gmail.com> (raw)
In-Reply-To: <eed550ec-96ac-4dd4-96e2-ce139db13a5b@www.fastmail.com>
On Mon, 28 Feb 2022 at 01:13, Andrew Jeffery <andrew@aj.id.au> wrote:
> Okay, so the root cause of this was I was setting RUST_{HOST,TARGET}_SYS
> to "powerpc64le-unknown-linux-gnu", which matched RUST_BUILD_SYS. I did
> that because rustc seems to be quite unhappy when supplied with
> `--target ppc64le-linux` or `--target powerpc64le-linux'. I'm trying to
> understand why, but I'm struggling because rustc seems just fine with
> `--target x86_64-linux` despite none of `ppc64le-linux`,
> `powerpc64le-linux` nor `x86_64-linux` appearing in the `rustc --print
> target-list` output that I could gather.
>
> How/why does `--target x86_64-linux` work?
I think in the context of oe-core, all targets are custom ones,
specified by writing out json files and directing rust to use them. So
you need to do two things:
1. --print target-list is useless and irrelevant, as it only prints
built-in targets, don't try it.
2. When there's a problem inspect what json files are in the sysroot,
what they contain, and whether rust is able to find them.
x86_64-linux.json is made specifically for building native items.
Alex
next prev parent reply other threads:[~2022-02-28 8:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 3:52 [RFC PATCH 0/8] rust: Fix powerpc64le support Andrew Jeffery
2022-02-22 3:52 ` [RFC PATCH 1/8] rust: Migrate arch_to_rust_target_arch() to rust-common class Andrew Jeffery
2022-02-22 10:05 ` [OE-core] " Richard Purdie
2022-02-23 0:41 ` Andrew Jeffery
2022-02-22 3:52 ` [RFC PATCH 2/8] rust: Rename arch_to_rust_target_arch() for generality Andrew Jeffery
2022-02-22 3:52 ` [RFC PATCH 3/8] rust: Handle Power arch variants in arch_to_rust_arch() Andrew Jeffery
2022-02-22 3:52 ` [RFC PATCH 4/8] rust: Consistently use RUST_{BUILD,HOST,TARGET}_{ARCH,SYS} Andrew Jeffery
2022-02-22 3:52 ` [RFC PATCH 5/8] rust: libstd-rs: Install deps under {RUST_,}TARGET_SYS mismatch Andrew Jeffery
2022-02-22 3:52 ` [RFC PATCH 6/8] rust: Mitigate duplicate sections on matching architectures Andrew Jeffery
2022-02-22 9:57 ` [OE-core] " Alexander Kanavin
2022-02-23 0:38 ` Andrew Jeffery
2022-02-28 0:13 ` Andrew Jeffery
2022-02-28 8:21 ` Alexander Kanavin [this message]
2022-02-28 13:57 ` Andrew Jeffery
2022-02-22 3:52 ` [RFC PATCH 7/8] rust: Add snapshot checksums for powerpc64le Andrew Jeffery
2022-02-22 9:59 ` [OE-core] " Alexander Kanavin
2022-02-22 12:28 ` Richard Purdie
2022-02-22 14:23 ` Alexander Kanavin
2022-02-22 18:34 ` Khem Raj
2022-02-22 23:41 ` Andrew Jeffery
2022-02-23 0:17 ` Andrew Jeffery
2022-02-22 23:49 ` Andrew Jeffery
2022-02-23 0:03 ` Richard Purdie
2022-02-23 0:27 ` Andrew Jeffery
2022-02-23 0:43 ` Richard Purdie
2022-02-22 3:52 ` [RFC PATCH 8/8] rust: Introduce RUST_BUILD_ARCH Andrew Jeffery
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=CANNYZj_21ZYm1vz33FbbmVZ5md-GaQEVpvbrtCNkbh5Ck-0snQ@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=andrew@aj.id.au \
--cc=openembedded-core@lists.openembedded.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 NNTP newsgroup(s).