From: "Vinay Kumar" <vinay.m.engg@gmail.com>
To: randy.macleod@windriver.com
Cc: richard.purdie@linuxfoundation.org,
openembedded-core@lists.openembedded.org,
steven@stevenwalter.org, johan.anderholm@gmail.com,
derek@asterius.io, cardoe@cardoe.com, dev@codyps.com,
tylerwhall@gmail.com, raj.khem@gmail.com,
vinay.kumar@blackfigtech.com, saul.wold@windriver.com,
martin.jansa@gmail.com, paul@pbarker.dev,
Vinay Kumar <vinay.m.engg@gmail.com>
Subject: [OE-core] [v4] [RFC] Merge meta-rust to oe-core
Date: Fri, 13 Aug 2021 08:19:47 -0700 [thread overview]
Message-ID: <20210813151947.55142-1-vinay.m.engg@gmail.com> (raw)
In-Reply-To: <aa7653eb-336f-ee08-3126-e6c790a9226f@windriver.com>
rust-common.inc: Fix build failure with qemuppc64.
The glibc build of "rust-hello-world" throws error in libstd-rs package.
error: unrecognized arch "powerpc64le" in target specification
The same got fixed by changing the arch to "powerpc64".
Signed-off-by: Vinay Kumar <vinay.m.engg@gmail.com>
---
meta/recipes-devtools/rust/rust-common.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/rust/rust-common.inc b/meta/recipes-devtools/rust/rust-common.inc
index 350517c723..f574152815 100644
--- a/meta/recipes-devtools/rust/rust-common.inc
+++ b/meta/recipes-devtools/rust/rust-common.inc
@@ -248,6 +248,8 @@ def arch_to_rust_target_arch(arch):
return "mips64"
elif arch == "armv7":
return "arm"
+ elif arch == "powerpc64le":
+ return "powerpc64"
else:
return arch
--
2.31.1
next prev parent reply other threads:[~2021-08-13 15:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 0:22 [v3] [RFC] Merge meta-rust to oe-core Randy MacLeod
2021-08-11 13:14 ` Randy MacLeod
2021-08-11 15:18 ` Randy MacLeod
2021-08-13 15:19 ` Vinay Kumar [this message]
2021-08-13 15:22 ` [OE-core] [v4] " Vinay Kumar
2021-08-17 14:52 ` Randy MacLeod
[not found] ` <169C1FA457B99CA0.23238@lists.openembedded.org>
2021-08-20 10:06 ` [OE-core] [v4] [RFC] Merge meta-rust to oe-core - Aug 19 update Randy MacLeod
2021-08-21 2:48 ` Randy MacLeod
2021-08-21 8:46 ` Richard Purdie
[not found] ` <169D3274AAECC435.19323@lists.openembedded.org>
2021-08-22 3:12 ` Randy MacLeod
2021-08-22 11:19 ` Richard Purdie
2021-08-22 12:45 ` Randy MacLeod
2021-08-23 9:21 ` Richard Purdie
2021-08-24 16:48 ` Randy MacLeod
[not found] ` <169E4C0C80951608.1595@lists.openembedded.org>
2021-08-27 4:05 ` Randy MacLeod
2021-08-27 9:03 ` Richard Purdie
[not found] ` <7A95231E-0879-46D6-8653-85338E9BDDFA@amazon.com>
2021-09-01 8:44 ` Richard Purdie
[not found] ` <16A0A6483A22DE64.7229@lists.openembedded.org>
2021-09-01 9:15 ` Richard Purdie
[not found] ` <169F1E62C63E8EDC.31425@lists.openembedded.org>
2021-08-27 12:04 ` Richard Purdie
[not found] ` <169F2844BF9C5B85.31425@lists.openembedded.org>
2021-09-01 8:38 ` Richard Purdie
2021-08-27 14:31 ` Armin Kuster
2021-08-27 20:09 ` Tim Orling
[not found] ` <169D9CED4738B0BB.18298@lists.openembedded.org>
2021-08-22 12:38 ` Richard Purdie
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=20210813151947.55142-1-vinay.m.engg@gmail.com \
--to=vinay.m.engg@gmail.com \
--cc=cardoe@cardoe.com \
--cc=derek@asterius.io \
--cc=dev@codyps.com \
--cc=johan.anderholm@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@windriver.com \
--cc=steven@stevenwalter.org \
--cc=tylerwhall@gmail.com \
--cc=vinay.kumar@blackfigtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.