public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] rust: Enable dynamic linking with llvm
Date: Wed, 18 Feb 2026 09:26:11 -0800	[thread overview]
Message-ID: <976428.1771435571945028979@lists.openembedded.org> (raw)
In-Reply-To: <5f3097df-5e24-41f8-9293-db01248e383c@windriver.com>

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

On Tue, Feb 17, 2026 at 07:54 PM, Randy MacLeod wrote:

> 
> I'm still a bit uncomfortable with changing the way that target Rust is
> built to deal with
> a Rust-native problem. Also there's the question about dynamic linking
> increasing runtime
> by a small amount. Finally, I worry that few people/distros change the
> default linking to by dynamic.
> 
> So I won't object to this work-around especially if we can easily limit it
> to -native. Have you tried that?

Hi Randy,

I’ve now limited the change as you suggested:
- rust-native links with LLVM dynamically
- rust-target links with LLVM statically

This keeps the workaround only in -native and avoids changing how the target toolchain is built.
I reran the relevant tests and didn’t see any regressions or runtime issues.
I’ll send V3 shortly with this approach.

Thanks,
Sunil Dora

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

  reply	other threads:[~2026-02-18 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 16:50 [PATCH] rust: Enable dynamic linking with llvm sunilkumar.dora
2026-02-12 17:05 ` [OE-core] " Ross Burton
2026-02-13 19:51   ` Dora, Sunil Kumar
2026-02-17 14:24     ` [OE-core] " Randy MacLeod
2026-02-18 17:26       ` Dora, Sunil Kumar [this message]
2026-02-12 17:52 ` Alexander Kanavin
2026-02-13 19:53   ` Dora, Sunil Kumar
2026-02-15 16:35 ` [OE-core] " Mathieu Dubois-Briand
2026-02-16 12:47   ` Dora, Sunil Kumar

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=976428.1771435571945028979@lists.openembedded.org \
    --to=sunilkumar.dora@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