Skip to content

Anchor build returns the below error always #14449

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

Closed
ghost opened this issue Aug 25, 2024 · 2 comments
Closed

Anchor build returns the below error always #14449

ghost opened this issue Aug 25, 2024 · 2 comments
Labels
C-bug Category: bug S-triage Status: This issue is waiting on initial triage.

Comments

@ghost
Copy link

ghost commented Aug 25, 2024

Problem

error: couldn't read \?\F:\scaff\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"));
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: this error originates in the macro include (in Nightly builds, run with -Z macro-backtrace for more info)

error: couldn't read \?\F:\scaff\anchor\target\sbf-solana-solana\release\build\typenum-255e67d6ee89f566\out/op.rs: The filename, directory name, or volume label syntax is incorrect. (os error 123)
--> src\lib.rs:72:5
|
72 | include!(concat!(env!("OUT_DIR"), "/op.rs"));
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: this error originates in the macro include (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not compile typenum (lib) due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile typenum (lib) due to previous error

Steps

No response

Possible Solution(s)

No response

Notes

No response

Version

cargo version : 1.80.1
@ghost ghost 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

@weihanglo
Copy link
Member

Close as duplicate. You may want to contat anchor build maintainer not to canonicalize paths to circumvent this bug, or try some other workarounds listed in #13919. Thank you.

@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
@weihanglo and others