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: 1074 bytes --]

Hi Benhur,

Thanks for v3. Tested on master with PACKAGECONFIG rust-analyzer enabled;
it works for me in a clean environment.

One issue I noticed, not from your patch but from the existing cargo
wrapper: on a host with rustup installed, rust-analyzer from the SDK
prefers the rustup cargo proxy (~/.cargo/bin/cargo) and sets
RUSTUP_TOOLCHAIN to the SDK sysroot.

The nativesdk cargo wrapper then exports LD_LIBRARY_PATH with the SDK
lib dirs, and the host-side rustc proxy that cargo runs for "rustc -vV"
gets the SDK's glibc 2.44 under the host loader:

rustc: symbol lookup error: .../lib/libc.so.6: undefined symbol:
__pointer_chk_guard, version GLIBC_PRIVATE

cargo metadata exits 101 and rust-analyzer falls back to a degraded mode.
Seen on Ubuntu 22.04 and 24.04 hosts; with an empty HOME (no rustup) it
works. So this is a pre-existing wrapper issue, your patch just makes it
reachable from rust-analyzer. I will report it separately.

Could you share your test setup, host distro/glibc and whether rustup
was present?

Thanks,
Sunil Dora

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