rust-embedded / rust-embedded/meta-rust-bin

Sysroot does not seem to be taken into account correctly in scarthgap

Open
#236 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
BitBake
Stars
124
Forks
92
Avg merge
6h 54m
Merged PRs (30d)
2

Description

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 ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Rust application recipe build with the Rust 1.95 commit on Yocto scarthgap, then inspect the rust-lld invocation and recipe sysroot paths. Compare the failing search paths with the Rust 1.89 build and verify whether host /usr/lib is being used. Done means the required libraries are resolved from the recipe sysroot and the application links successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
build-system, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.