rust-lang / rust-lang/rustc_apfloat

x86_64-pc-windows-msvc build failing: expected `src/lib.rs` to start with:

Open
#10 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
23
Forks
16
Avg merge
6h 52m
Merged PRs (30d)
1

Description

building 2ced82cdd61e163b9b07e33686c1ed78de2b01af failed:

error: failed to run custom build command for `rustc_apfloat v0.2.0+llvm-462a31f5a5ab (G:\projs\rustc_apfloat)`

Caused by:
  process didn't exit successfully: `G:\projs\rustc_apfloat\target\debug\build\rustc_apfloat-cd007fccae510ac7\build-scri
pt-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs

  --- stderr

  expected `src/lib.rs` to start with:

  //! Port of LLVM's APFloat software floating-point implementation from the
  //! following C++ sources (please update commit hash when backporting):
  //! https://github.com/llvm/llvm-project/commit/

  thread 'main' panicked at 'failed to validate `src/lib.rs`'s commit hash (see above)', build.rs:32:13
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Probably line ending mismatch?

Reproduce: clone master branch, build with cargo build on x86_64-pc-windows-msvc.

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 build.rs around the validation reported at line 32 and compare it with the opening of src/lib.rs. Reproduce with cargo build on x86_64-pc-windows-msvc, checking the reported line-ending or header mismatch; done means the Windows build passes the existing source-header validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.