From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: [PATCH 4/6] rust-common.bbclass: Define rust arch for x32 platforms
Date: Fri, 1 Dec 2023 10:33:52 -0800 [thread overview]
Message-ID: <20231201183356.311137-4-raj.khem@gmail.com> (raw)
In-Reply-To: <20231201183356.311137-1-raj.khem@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta/classes-recipe/rust-common.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes-recipe/rust-common.bbclass b/meta/classes-recipe/rust-common.bbclass
index 3d73a370ec8..5bdaf0c7a69 100644
--- a/meta/classes-recipe/rust-common.bbclass
+++ b/meta/classes-recipe/rust-common.bbclass
@@ -63,6 +63,8 @@ def rust_base_triple(d, thing):
# This catches ARM targets and appends the necessary hard float bits
if os == "linux-gnueabi" or os == "linux-musleabi":
libc = bb.utils.contains('TUNE_FEATURES', 'callconvention-hard', 'hf', '', d)
+ if os == "linux-gnux32" or os == "linux-muslx32":
+ libc = ""
elif "musl" in os:
libc = "-musl"
os = "linux"
--
2.43.0
next prev parent reply other threads:[~2023-12-01 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 18:33 [PATCH v12 1/6] vte: upgrade 0.72.2 -> 0.74.0 Khem Raj
2023-12-01 18:33 ` [PATCH v12 2/6] vte: Upgrade to 0.74.1 Khem Raj
2023-12-01 18:33 ` [PATCH v12 3/6] vte: Separate out gtk4 pieces of vte into individual packages Khem Raj
2023-12-01 18:33 ` Khem Raj [this message]
2023-12-01 18:33 ` [PATCH 5/6] virglrenderer: Fix build with clang Khem Raj
2023-12-01 18:33 ` [PATCH 6/6] llvm: Upgrade to 17.0.6 Khem Raj
2023-12-01 23:27 ` [OE-core] " Alexandre Belloni
[not found] ` <179CD8EAC4F00896.18076@lists.openembedded.org>
2023-12-01 23:55 ` Alexandre Belloni
2023-12-02 0:03 ` Khem Raj
2023-12-02 0:10 ` Khem Raj
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=20231201183356.311137-4-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--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