Could not compile in release. File name too long.
Open
Nobody has claimed this yet.
C-bug
needs-triage
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
I tried to compile this repository https://github.com/coolcatcoder/mind_control_retry with cargo run --release.
(This does not happen in debug, only release.)
I expected it to compile.
Instead, this happened:
error: could not write output to /home/coolcatcoder/Documents/GitHub/mind_control_retry/target/release/deps/230fb44afa6e3556-8bcaa95a9ca3f52.bevy_transform_interpolation-bbcabe0d7d92346f.bevy_transform_interpolation.12ba7750790b6058-cgu.0.rcgu.o.rcgu.o: File name too long
Meta
rustc --version --verbose:
rustc 1.92.0-nightly (695857bc3 2025-10-21)
binary: rustc
commit-hash: 695857bc3f72ec4f59c79f323460fe488c38a53f
commit-date: 2025-10-21
host: x86_64-unknown-linux-gnu
release: 1.92.0-nightly
LLVM version: 21.1.3
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 cargo run --release with the linked mind_control_retry repository on the reported nightly Rust toolchain. Investigate how the release build produces the object-file path shown in the error and verify the fix by confirming that the project compiles successfully without a “File name too long” failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100