-
Notifications
You must be signed in to change notification settings - Fork 165
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
"cannot link object files with different floating-point ABI" rustc 1.56.0-nightly (2021-08-06) #85
Comments
Are you using the latest |
oh sorry. I updated riscv crate to the latest 0.7.0 and that fixed the error. |
bors bot
added a commit
to rust-embedded/riscv-rt
that referenced
this issue
Sep 19, 2021
79: update to riscv 0.7 r=almindor a=smsxgli hi everyone, I am a new guy with both github, rust and riscv, and this is my first PR, so if I miss something or do something wrong, please let me know (and forgive my poor english, since I am not a native speaker). crate `riscv` v0.7 solved link error about [`different hardware float abi`](rust-embedded/riscv#85), but riscv-rt still depend on `riscv` v0.6. Co-authored-by: smsxgli <[email protected]>
romancardenas
pushed a commit
that referenced
this issue
Nov 17, 2023
79: update to riscv 0.7 r=almindor a=smsxgli hi everyone, I am a new guy with both github, rust and riscv, and this is my first PR, so if I miss something or do something wrong, please let me know (and forgive my poor english, since I am not a native speaker). crate `riscv` v0.7 solved link error about [`different hardware float abi`](#85), but riscv-rt still depend on `riscv` v0.6. Co-authored-by: smsxgli <[email protected]>
romancardenas
pushed a commit
that referenced
this issue
Nov 17, 2023
86: Update CHANGELOG.md r=almindor a=parkero Adds currently unreleased changes for #85 Co-authored-by: parkero <[email protected]>
romancardenas
pushed a commit
that referenced
this issue
Nov 17, 2023
87: release v0.8.1 r=Disasm a=almindor Release v0.8.1 to fix #85 Co-authored-by: Ales Katona <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that the latest nightly build has the same issue as #69.
output:
rustup show:
The text was updated successfully, but these errors were encountered: