rust-osdev / rust-osdev/bootimage

Error: Failed to find kernel binary in cargo metadata output

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

Nobody has claimed this yet.

Dominant language
Rust
Stars
906
Forks
70
PR merge metrics
No merged PRs in 30d

Description

I was following the OS tutorial, and ran into an issue when using cargo bootimage.

→ cargo bootimage --target ./x64_86-darkos.json                                                                                                                                                                           
Building kernel
   Compiling compiler_builtins v0.1.105
   Compiling core v0.0.0 (C:\Users\ticta\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core)
   Compiling bootloader v0.9.23
   Compiling rustc-std-workspace-core v1.99.0 (C:\Users\ticta\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\rustc-std-workspace-core)
   Compiling os v0.1.0 (C:\Users\ticta\Deno\os)
    Finished dev [unoptimized + debuginfo] target(s) in 21.97s
Error: Failed to find kernel binary in cargo metadata output

When looking through to target folder, it did spit out a file that looks to be the kernel binary:
image

Not exactly sure how to solve this issue.

My os is Windows (11) and my cargo version is cargo 1.77.0-nightly (1ae631085 2024-01-17)

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

Reproduce cargo bootimage --target ./x64_86-darkos.json on Windows 11 and compare the cargo metadata output with the binary produced in the target folder. Start with the bootimage handling of cargo metadata and the x64_86-darkos.json target; done means the generated kernel binary is correctly identified instead of reporting that it is missing.

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.