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.
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