-
Notifications
You must be signed in to change notification settings - Fork 132
nightly: cannot open linker script file -Wl,--gc-sections #857
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
Comments
Please provide all information to reproduce. |
I don't know what all you need. Attached is a workspace containing just the project that doesn't build, as well as the full compile log (or at least what the console showed when it had failed). |
Note that this workspace is the way it is after attempting to build with the nightly. If I subsequently try to build with 4.1, it fails in the same way. So: Starting with:
|
Actually it's even worse than that. In step 2 above there's no need to build. Just opening the workspace with the nightly screws up the project to the point where it can no longer be built with either the nightly or with 4.1. |
I havn't had time to take a look yet. But steps to reproduce should start from "any workspace" not "this workspace" |
Can this be closed? |
Fine by me. I've stopped using Sloeber, largely because of this issue. I couldn't confirm that it's fixed even if you did fix it. |
Thanks for the uplifting comment. |
I updated to the nightly to get the fix for #856. Now my older project will no longer build:
Grepping around in .settings/org.eclipse.cdt.core.prefs finds mentions of
-T${A.BUILD.FLASH_LD}
which makes me think that that variable should be set but isn't. I tried adding it to the C/C++ Build Environment but that didn't help. I'm a bit stumped because I'm not familiar with how Eclipse manages projects and handles compilation.The text was updated successfully, but these errors were encountered: