Re: [PATCH v3] rust: add rust-analyzer to the SDK behind a PACKAGECONFIG

["Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>]

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

On Fri, Nov 13, 2026 at 12:17 PM, Khem Raj wrote:

> 
> binary is started by the system loader, but then picks up a libc.so.6 from
> some other glibc tree
> (the.../lib/ in the message). That libc wants a private symbol the system
> loader doesn’t
> provide, so rustc dies before doing anything.
> 

Yes. This looks like the same issue as YOCTO #15579 / #15735.
Two patches to drop the wrapper were posted in early 2025 and not merged,
the concern being the libncurses case the wrapper was added for in 388e7cac9f ( https://git.openembedded.org/openembedded-core/commit/?id=388e7cac9f90e79ce8c3c1683d8ee0f4df1bc907 ).

What has changed since then is glibc 2.44: the pointer guard moved to a
GLIBC_PRIVATE symbol exported by ld.so, so any host loader older than
2.44 now fails deterministically on the SDK libc:

https://sourceware.org/git/?p=glibc.git;a=commit;h=a5ec880f808ee7268d985bed4f961799bdc0a4bf

With rust-analyzer in the SDK this will be hit by anyone who has rustup
installed, so it may be worth revisiting. How would you like this tracked?

Thanks,
Sunil Dora

> 
> 
>

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