Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fails with "filename, directory name, or volume label syntax is incorrect" error in typenum crate #14450

Closed
OmChillure opened this issue Aug 25, 2024 · 1 comment
Labels
C-bug Category: bug S-triage Status: This issue is waiting on initial triage.

Comments

@OmChillure
Copy link

Problem

When attempting to build my Anchor project, I'm encountering consistent errors related to the typenum crate. The build process is unable to read the "op.rs" file, resulting in multiple errors.

Error message:
error: couldn't read \?\F:\scaff\journal\anchor\target\release\build\typenum-b4aec6864503f063\out/op.rs: The filename, directory name, or volume label syntax is incorrect. (os error 123)
--> C:\Users\Om Chillure.cargo\registry\src\index.crates.io-6f17d22bba15001f\typenum-1.17.0\src\lib.rs:72:5
|
72 | include!(concat!(env!("OUT_DIR"), "/op.rs"));
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Steps

  1. Create a new Anchor project
  2. Add necessary dependencies
  3. Run anchor build

Possible Solution(s)

No response

Notes

  • This error occurs consistently across multiple builds.
  • I've tried cleaning the project and rebuilding, but the issue persists.
  • The error seems to be related to file paths, possibly due to Windows path length limitations or permissions issues.

Version

Environment:
- Operating System: Windows 11
- Rust version: 1.80.1
- Cargo version: 1.80.1
- Anchor version: 0.30.1
- Solana version: 1.18.16
- Typenum version: 1.17.0
@OmChillure OmChillure added C-bug Category: bug S-triage Status: This issue is waiting on initial triage. labels Aug 25, 2024
@weihanglo
Copy link
Member

Thanks for the report. This seems to be a duplicate of #13919 and #14449. Close in favour of them

@weihanglo weihanglo closed this as not planned Won't fix, can't repro, duplicate, stale Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug S-triage Status: This issue is waiting on initial triage.
Projects
None yet
Development

No branches or pull requests

2 participants