fuchsia targets building error: unresolved import `object`
Open
Nobody has claimed this yet.
C-bug
O-fuchsia
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
rustc 1.95.0-nightly (e96bb7e44 2026-01-27)
compile with -Zbuild-std and panic-immediate-abort for all fuchsia targets
there is no problem in nightly-2026-01-26
unresolved import `object`
╭▸ /rustc/e96bb7e44fbcc23c1e6009e8d0ee8ab208668fb4/library/std/src/../../backtrace/src/print/fuchsia.rs:4:5
│
4 │ use object::NativeEndian as NE;
│ ━━━━━━ use of unresolved module or unlinked crate `object`
│
╰ help: if you wanted to use a crate named `object`, use `cargo add object` to add it to your `Cargo.toml`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with -Zbuild-std and panic-immediate-abort for the Fuchsia targets, then inspect library/std/src/../../backtrace/src/print/fuchsia.rs and compare against nightly-2026-01-26. Done means the affected Fuchsia targets build without the unresolved object import.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, compilers, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100