-
Notifications
You must be signed in to change notification settings - Fork 46
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
no memory region specified for section '.eh_frame' (Ubuntu 16 i686) #96
Comments
i am not at all sure this is it but, usually with ARM we specify the GNU/gcc linker rather than LLD with
have you tried building with the appropriate GNU linker for riskv? also may be related to: rust-embedded/wg#36 (comment) |
|
That's with
|
However with
I didn't get any error:
|
I am able to see the binary file, as described here - it is just I have my toolchain offers "riscv32-unknown-elf" prefix, for the executibles, instead of "riscv-nuclei-elf-" |
ahh [target.thumbv7em-none-eabihf]
rustflags = [
"-C", "linker=arm-none-eabi-gcc",
"-C", "link-arg=-L/usr/lib/arm-none-eabi/lib/thumb/v7e-m/fpv4-sp/hard/",
]
great! you should just be able to change file paths then? |
@lupyuen , could you help here? Let's ask those who know how to do that properly.
CC @zsdonghao @junhuanchen @myuanz @QinYUN575 @btx000 @pcotret @Zepan @MindShow |
It says |
I could try to reproduce again an share all generated artifacts |
The only problem I had related to this was that my Longan Nano was kinda stuck.
|
Who is "we" and why are you doing that? |
I see that something is rather wrong with the config. For instance I tried to build https://github.com/pdx-cs-rust/nanoball - but it failed, with my recent ~/.cargo/config file. |
org project, because inexplicably when you start linking external c libraries the linker seems to break in a variety of horrifying ways / stop being able to infer a bunch of things like this correctly.
oh yeah this is, v different from what i was thinking. |
@barafael , experiencing an uncertain situation with your demos: |
Hi.
I believe you know the cause of this bug.
The text was updated successfully, but these errors were encountered: