-
Notifications
You must be signed in to change notification settings - Fork 223
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
cargo build - error[E0658] - proc_macro::Literal::byte_character(byte) #535
Comments
I just re-ran RustUp Update, what didn't get listed in what I have done and nothing has changed since a 1~2 hours ago:
|
Adding the suggested 'help' lines:
to /home/hp/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.80/src/lib.rs, allowed to progress a little bit more, But still ended with errors:
|
I had this issue as well. I resolved it by updating the rust-toolchain.toml file to target v1.79.0-nightly like so:
|
Hi,
Now, having to figure out about the 'cargo embed' "Error No supported probe was found" issue. I am wondering if what I just done... :
is enough (?) to ensure that everything else attempted before "Flashing" the device is in good order from now on, Or if I have to try to set up everything from scratch in a VM and compare the results... ? 🤔 Thanks for reading thus far ! 😃 Best regards, |
Thanks @calebarapp for the tip. 👍 This seems to risk to be cancelled out if you run rustup update, isn't it ? Maybe preferable to do rustup override set nightly-yyyy-mm-dd from the project / package directory like in the following example:
where you replace yyyy-mm-dd by 2024-04-11 or whatever date you need. Best regards, |
There is a lot of chaotic information in this issue, not even sure where to start... @HaroPo, it seems to me you have quite a few misunderstanding on how the entire thing is supposed to fit together. We can clear these things up, but first let me focus on the issue at hand. At the core stands a regression caused by
|
I've created a new issue #537 to track work on a solution. This will keep things a bit cleaner than trying to do it here. @HaroPo: For your information, here are a few pointers to get you back on the right track:
Don't do this, use the
That compiler version is entirely too old. Stick to the one from the You also should not set an override using rustup when a
Don't ever edit files in
Yes, you need
No, no, no, why are you trying to use
No.
Avoid |
@Rahix My apologies for the late reply (I've got private issues keeping me very busy until now) and I also apologies for the mess here, as all I have done (wrongly) before, comes from starting with whatever "HowTos" from Google Search results until I eventually end on your project. I would like to make a better (or up to date) "How To" for other beginners as soon as I can free enough disk space on my PC to run a VM and redo all the Rust Language setup from scratch for the purpose, because I just successfully followed the provided instructions from the QuickStart section of your README file:
And it works fine straight away ! 😃 @HaroPo @Rahix Best regards, P.S.
@HaroPo and all other beginners like I am at the writing time of this: Full details as a "snapshot" sample of what happens in the terminal window when things are OK:
|
You can use the "discussions" in this project to ask user questions: https://github.com/Rahix/avr-hal/discussions For general rust questions you can find help in the rust-lang forum: https://users.rust-lang.org/ And finally, there is an avr-rust matrix channel: https://matrix.to/#/#avr-rust_Lobby:gitter.im |
Hi
I am a "baby beginner" with Rust and wanted to learn about Rust for embedded programming on 8-bit AVR MCUs...
I am facing errors at "cargo build" time and I wonder what I am supposed to do with the suggested 'help' lines:
In case you are interested to reproduce the issue that I am facing, I am providing the following information:
After managing to get RustUp installed and running, I started to deal with the following online resources information blogs to get thing setup:
After a LOT a attempts, it always ended cycling infinitely with a bunch of errors whatever I changed as indicated. => Gave up + Go to bed .
Having to try later with a STM32 Nucleo board taking time to come via mail...
What ends into:
After searching clues in different ways, I ended with this:
%23![feature(proc_macro_byte_character)]
+to+the+crate+attributes+to+enableI still wonder where exactly to add those lines:
since the errors persist despite adding them to:
or / and
and also trying:
... 🤔
Additionally, there is also some recent (8 hours ago) activity there:
I will then wait for news from the involved GitHub communities if unable to progress during the next coming hours.
Thank you for reading thus far.
Best regards,
HP_
The text was updated successfully, but these errors were encountered: