We have a project using yocto scarthgap (yocto-5.0.17) and the meta-rust-bin.
On the Rust 1.89 commit (a354523d1a86d9dd3f7eb0fa2a0208156382c8ac), our rust application recipes builds correctly.
When we updated to Rust 1.95 (4aac047a58d0e58d6ff9293d93fc3dba226f299f) the link fails, with the message:
rust-lld: error: cannot open /usr/lib/libm.so.6: No such file or directory.
Depending on which computer we build it, the missing library is changing based on what we have on the OS /usr/lib (not the ones in the recipe sysroot).
libm.so.6 and the other required libs are correctly found in the recipe sysroot.
It's like the linker is trying to search libraries in the host system rather than in the recipe sysroot.
Is there a kind of incompatibility between newest version of this meta and older yocto versions ?
We have a project using yocto scarthgap (yocto-5.0.17) and the meta-rust-bin.
On the Rust 1.89 commit (
a354523d1a86d9dd3f7eb0fa2a0208156382c8ac), our rust application recipes builds correctly.When we updated to Rust 1.95 (
4aac047a58d0e58d6ff9293d93fc3dba226f299f) the link fails, with the message:rust-lld: error: cannot open /usr/lib/libm.so.6: No such file or directory.Depending on which computer we build it, the missing library is changing based on what we have on the OS
/usr/lib(not the ones in the recipe sysroot).libm.so.6and the other required libs are correctly found in the recipe sysroot.It's like the linker is trying to search libraries in the host system rather than in the recipe sysroot.
Is there a kind of incompatibility between newest version of this meta and older yocto versions ?