Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Deepesh Varatharajan <deepesh.varatharajan@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	Shivaprasad.Moodalappa@windriver.com,
	Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH 2/5] rust: Fix build failure when multilibs are enabled
Date: Tue, 25 Mar 2025 10:14:11 +0530	[thread overview]
Message-ID: <b1c48246-eb87-4a40-918f-31a41faf8a7e@windriver.com> (raw)
In-Reply-To: <CANNYZj_5kjhg3WPi7E-UxYX2yFXw-KFpR0gdExet79uG-Xin_A@mail.gmail.com>


On 24-03-2025 14:53, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Fri, 21 Mar 2025 at 14:25, Varatharajan, Deepesh via
> lists.openembedded.org
> <deepesh.varatharajan=windriver.com@lists.openembedded.org> wrote:
>> From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
>>
>> When multilibs are enabled, rustc could not find dynamic libraries in the
>> lib64 directory due to the bootstrapping process searching in the lib
>> directory. This commit exports both lib and lib64 paths to ensure
>> correct library detection.
> What is creating and populating this lib64 directory then, and how
> does it decide that it should be named 'lib64'? Shouldn't either that,
> or the code that looks in 'lib' be fixed so they match each other?
>
> This looks like an incomplete fix, as it does not get to the bottom of
> the mismatch problem.
>
> Alex
Sure Alex, I will investigate further.

Deepesh


  parent reply	other threads:[~2025-03-25  4:44 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
2025-03-27  6:26       ` Deepesh Varatharajan
2025-03-25  4:44     ` Deepesh Varatharajan [this message]
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=b1c48246-eb87-4a40-918f-31a41faf8a7e@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 \
    /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