-
Notifications
You must be signed in to change notification settings - Fork 175
use LLD as the default linker #41
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Also I have no idea how to improve visibility.
Hi. I am a beginner. Thanks for working on this. I experienced the issue described in # 92 today. |
bors r=therealprof,korken89 |
41: use LLD as the default linker r=therealprof,korken89 a=japaric closes #39 I added instructions on how to switch to a different linker to .cargo/config but I don't think that's too visible. Beginners are unlikely to look into that file if they run into problems with the default linker. Any suggestions to improve the visibility of that information? Also, don't merge this until the default linker changes for the Cortex-M targets on nightly as this relies on that change. r? @rust-embedded/cortex-m Co-authored-by: Jorge Aparicio <[email protected]>
Build failed |
Last commit should fix the build errors. re-r? |
bors r+ |
41: use LLD as the default linker r=therealprof a=japaric closes #39 I added instructions on how to switch to a different linker to .cargo/config but I don't think that's too visible. Beginners are unlikely to look into that file if they run into problems with the default linker. Any suggestions to improve the visibility of that information? Also, don't merge this until the default linker changes for the Cortex-M targets on nightly as this relies on that change. r? @rust-embedded/cortex-m Co-authored-by: Jorge Aparicio <[email protected]>
Build succeeded |
closes #39
I added instructions on how to switch to a different linker to .cargo/config but
I don't think that's too visible. Beginners are unlikely to look into that file
if they run into problems with the default linker. Any suggestions to improve
the visibility of that information?
Also, don't merge this until the default linker changes for the Cortex-M targets
on nightly as this relies on that change.
r? @rust-embedded/cortex-m