rust-osdev / rust-osdev/bootloader

ovmf-prebuilt v0.1.0-alpha.1 doesn't compile

Open
#361 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.7k
Forks
240
PR merge metrics
No merged PRs in 30d

Description

The result i get when I compile with cargo 1.70.0-nightly (15d090969 2023-03-21) is listed below. What am I missing?
I'm following the migration guide from 0.9.

Compiling ovmf-prebuilt v0.1.0-alpha.1
error[E0463]: can't find crate for std
|
= note: the x86_64-unknown-none target may not support the standard library
= note: std is required by ovmf_prebuilt because it does not declare #![no_std]
= help: consider building the standard library from source with cargo build -Zbuild-std

error[E0463]: can't find crate for std
--> /home/zingo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ovmf-prebuilt-0.1.0-alpha.1/src/lib.rs:1:5
|
1 | use std::path::{PathBuf, Path};
| ^^^ can't find crate
|
= note: the x86_64-unknown-none target may not support the standard library
= help: consider building the standard library from source with cargo build -Zbuild-std

error: cannot find macro assert in this scope
--> /home/zingo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ovmf-prebuilt-0.1.0-alpha.1/src/lib.rs:5:5
|
5 | assert!(path.exists(), "OVMF-pure-efi.fd does not exist");
| ^^^^^^
|
= help: consider importing this macro:
core::assert

error: cannot find macro env in this scope
--> /home/zingo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ovmf-prebuilt-0.1.0-alpha.1/src/lib.rs:4:26
|
4 | let path = Path::new(env!("CARGO_MANIFEST_DIR")).join("OVMF-pure-efi.fd");
| ^^^
|
= help: consider importing this macro:
core::env

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 the 0.9 migration guide and the installed ovmf-prebuilt src/lib.rs shown in the compiler output, then reproduce the build using the reported nightly toolchain and x86_64-unknown-none target. Determine whether the migration instructions or the crate's standard-library assumptions are responsible, and document or verify a working build outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.