Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: deepesh.varatharajan@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: Mon, 24 Mar 2025 13:48:24 -0400	[thread overview]
Message-ID: <6b60bdbd-8095-432f-b3fe-37057b1cb086@windriver.com> (raw)
In-Reply-To: <CANNYZj_5kjhg3WPi7E-UxYX2yFXw-KFpR0gdExet79uG-Xin_A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

On 2025-03-24 5:23 a.m., Alexander Kanavin via lists.openembedded.org wrote:
> 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.

FYI:

This will block the 1.84 update until we understand the root cause.
What happened in 1.84 that we need this change?


../Randy



> Alex
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#213520):https://lists.openembedded.org/g/openembedded-core/message/213520
> Mute This Topic:https://lists.openembedded.org/mt/111827575/3616765
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [randy.macleod@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

-- 
# Randy MacLeod
# Wind River Linux

[-- Attachment #2: Type: text/html, Size: 3115 bytes --]

  reply	other threads:[~2025-03-24 17:48 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 [this message]
2025-03-25  8:35       ` Deepesh Varatharajan
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=6b60bdbd-8095-432f-b3fe-37057b1cb086@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=Shivaprasad.Moodalappa@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=deepesh.varatharajan@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