rust-lang / rust-lang/backtrace-rs

Doesn't build in no_std env but it seems like it is supposed to build there

Open
#438 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
628
Forks
291
PR merge metrics
No merged PRs in 30d

Description

I wanted to use this library in a no_std environment, but it doesn't compile because of the miniz_oxide crate. If I see it correctly in Cargo.toml and lib.rs, this crate is supposed to work in no_std-environments.

I'd like to propose the following changes:

  1. clarify in README.md if this crate actually supports no_std and what one has to do for it
  2. if this is a bug, please fix it and perhaps add some CI which covers this in the future

The build error for my x86_64 no_std-target is:

Compiling miniz_oxide v0.4.4
error[E0463]: can't find crate for `std`
  |
  = note: the `x86_64-unknown-hedron-5835702812158589728` target may not support the standard library
  = note: `std` is required by `miniz_oxide` because it does not declare `#![no_std]`
  = help: consider building the standard library from source with `cargo build -Zbuild-std`

For more information about this error, try `rustc --explain E0463`. 

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 with Cargo.toml and lib.rs to verify the crate's advertised no_std configuration and inspect how miniz_oxide is included. Reproduce the reported x86_64 no_std build error, then check README.md and the CI configuration for the documented support and coverage expected by the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.