From: Deepesh.Varatharajan@windriver.com
To: openembedded-core@lists.openembedded.org
Cc: Shivaprasad.Moodalappa@windriver.com,
Sundeep.Kokkonda@windriver.com,
Deepesh.Varatharajan@windriver.com
Subject: [PATCH V4 1/3] rust: Fix build break because of download-ci-llvm
Date: Wed, 5 Mar 2025 05:44:53 -0800 [thread overview]
Message-ID: <20250305134459.2275598-1-Deepesh.Varatharajan@windriver.com> (raw)
From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Previously, download-ci-llvm was set to false. However, with the following commit:
https://github.com/rust-lang/rust/commit/7d579046c80d3de3143dcb8b2db5640f95b5383c ,
which has been present from rust_1.83, it was changed to true. As a result, after
updating to rust_1.83, we encountered the following error during the build:
-------------------------------------------------------------------------------
| thread 'main' panicked at src/core/config/config.rs:2047:13:
| setting build-target.llvm-config is incompatible with download-ci-llvm.
| note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
-------------------------------------------------------------------------------
To resolve this issue, we are setting download-ci-llvm back to false.
Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
---
meta/recipes-devtools/rust/rust_1.82.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/rust/rust_1.82.0.bb b/meta/recipes-devtools/rust/rust_1.82.0.bb
index c4f8ee7108..cd470b1883 100644
--- a/meta/recipes-devtools/rust/rust_1.82.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.82.0.bb
@@ -129,6 +129,7 @@ python do_configure() {
# [llvm]
config.add_section("llvm")
config.set("llvm", "static-libstdcpp", e(False))
+ config.set("llvm", "download-ci-llvm", e(False))
if "llvm" in (d.getVar('TC_CXX_RUNTIME') or ""):
config.set("llvm", "use-libcxx", e(True))
--
2.43.0
next reply other threads:[~2025-03-05 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:44 Deepesh.Varatharajan [this message]
2025-03-05 13:44 ` [PATCH V4 2/3] rust: Upgrade 1.82.0->1.83.0 Deepesh.Varatharajan
2025-03-07 21:02 ` [OE-core] [PATCH V4 2/3] rust: Upgrade 1.82.0->1.83.0 --> bloat alert !! Randy MacLeod
2025-03-07 23:37 ` Richard Purdie
2025-03-13 18:48 ` Randy MacLeod
2025-03-14 12:32 ` Yash Shinde
2025-03-14 12:52 ` Yash Shinde
2025-03-14 13:48 ` Randy MacLeod
2025-03-14 15:50 ` Yash Shinde
2025-03-18 0:35 ` Randy MacLeod
2025-03-18 10:34 ` Yash Shinde
2025-03-12 9:52 ` [OE-core] [PATCH V4 2/3] rust: Upgrade 1.82.0->1.83.0 Alexander Kanavin
2025-03-14 4:38 ` Deepesh Varatharajan
2025-03-05 13:44 ` [PATCH V4 3/3] rust: Oe-selftest changes for rust v1.83.0 Deepesh.Varatharajan
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=20250305134459.2275598-1-Deepesh.Varatharajan@windriver.com \
--to=deepesh.varatharajan@windriver.com \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=Sundeep.Kokkonda@windriver.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