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

[SOLVED] Compile error using "cargo install xplr" #12

Closed
vdoma opened this issue Apr 6, 2021 · 7 comments
Closed

[SOLVED] Compile error using "cargo install xplr" #12

vdoma opened this issue Apr 6, 2021 · 7 comments

Comments

@vdoma
Copy link

vdoma commented Apr 6, 2021

I received the following error when using "cargo install xplr" on ubuntu. Any suggestions?

error: no rules expected the token `,`
   --> /home/vdoma/.cargo/registry/src/github.mirror.nvdadr.com-1ecc6299db9ec823/xplr-0.3.1/src/input.rs:373:29
    |
373 |                 | Self::Num9,
    |                             ^ no rules expected this token in macro call

error: aborting due to previous error

error: could not compile `xplr`.
@sayanarijit
Copy link
Owner

Weird... Can you please provide the output of rustc --version? Also, the Ubuntu version?

@idmyn
Copy link

idmyn commented Apr 6, 2021

I got this error too: rustc 1.45.0 (5c1f21c3b 2020-07-13) macOS Catalina (10.15.7)

@sayanarijit
Copy link
Owner

sayanarijit commented Apr 6, 2021

Probably because of rust-lang/rust#74880 which was fixed in rustc 1.48.0.

Can you try the latest version of Rustc? or you can also download the standalone binary tarball.

@idmyn
Copy link

idmyn commented Apr 6, 2021

Yeah it installed happily after I updated my rust version :)

@sayanarijit
Copy link
Owner

Nice. I'll rename and keep this issue open for others having the same issue.

@sayanarijit sayanarijit changed the title Compile error using "cargo install xplr" [SOLVED] Compile error using "cargo install xplr" Apr 6, 2021
@vdoma
Copy link
Author

vdoma commented Apr 6, 2021

I was using rustc version 1.47.0 on Ubuntu 20.10. Upgraded to rustc 1.51.0 and the problem went away. Thanks!

@sayanarijit
Copy link
Owner

FIxed: #42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants