From: Deepesh Varatharajan <deepesh.varatharajan@windriver.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: openembedded-core@lists.openembedded.org,
Shivaprasad.Moodalappa@windriver.com,
Sundeep.Kokkonda@windriver.com, alex.kanavin@gmail.com
Subject: Re: [OE-core] [PATCH 2/5] rust: Fix build failure when multilibs are enabled
Date: Tue, 25 Mar 2025 14:05:02 +0530 [thread overview]
Message-ID: <4004d896-bfce-4184-ab8e-88997ac5cc7d@windriver.com> (raw)
In-Reply-To: <6b60bdbd-8095-432f-b3fe-37057b1cb086@windriver.com>
On 24-03-2025 23:18, Randy MacLeod wrote:
> This will block the 1.84 update until we understand the root cause.
> What happened in 1.84 that we need this change?
The issue has existed before, but with the new commit
(https://github.com/rust-lang/rust/commit/68034f837a39387e49fc7d7c5b088f5372a1127e)
from Rust 1.83, an error has started occurring. The problem is that when
multilibs are enabled, stage1/rustc can't find the lib*.so files in the
lib directory, as they are now placed in the lib64 directory. To resolve
this, we initially reverted that commit. However, with the current
update, we removed that revert patch. To resolve this issue, we exported
the LD_LIBRARY_PATH to include both lib and lib64. After doing so, the
issue was resolved.
Deepesh
next prev parent reply other threads:[~2025-03-25 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 13:24 [PATCH 1/5] rust: Fix bloat issue in recent rust updates Deepesh.Varatharajan
2025-03-21 13:24 ` [PATCH 2/5] rust: Fix build failure when multilibs are enabled Deepesh.Varatharajan
2025-03-24 9:23 ` [OE-core] " Alexander Kanavin
2025-03-24 17:48 ` Randy MacLeod
2025-03-25 8:35 ` Deepesh Varatharajan [this message]
2025-03-27 6:26 ` Deepesh Varatharajan
2025-03-25 4:44 ` Deepesh Varatharajan
2025-03-21 13:24 ` [PATCH 3/5] rust: Fix build break because of "download-rustc" and "llvm-tools" Deepesh.Varatharajan
2025-03-21 13:24 ` [PATCH 4/5] rust: Upgrade 1.83.0->1.84.1 Deepesh.Varatharajan
2025-03-21 13:24 ` [PATCH 5/5] rust: Oe-selftest changes for rust v1.84.1 Deepesh.Varatharajan
2025-03-22 6:50 ` [OE-core] [PATCH 1/5] rust: Fix bloat issue in recent rust updates Khem Raj
2025-03-24 22:28 ` 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=4004d896-bfce-4184-ab8e-88997ac5cc7d@windriver.com \
--to=deepesh.varatharajan@windriver.com \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox