-
Notifications
You must be signed in to change notification settings - Fork 128
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
Linker issues with newlib version 4.4.0 #1160
Comments
Is the output above shortened? The text says "warning: _getentropy is not implemented and will always fail", so only a warning and the first actual error in your trace is "error: ld returned 1 exit status". Weird. Anyways, there is no support in modm for GCC 13 (and associated linker and lib versions) yet (see #1012), so this bug will probably not get fixed immediately. |
Maybe getentropy needs to be stubbed? But in general it's best not to mix newlib and gcc versions. The official ARM toolchains have a compatible new,ib version. |
Yeah, no problem that there is no "immediate" fix. I wanted to document this anyways in case other people run into this issue. I used to have other weird problems with the gcc 12 that my system shipped... and besides the protothreads, gcc 13 works okay. Thanks for the quick replies 🥰🥰 |
After upgrading
arm-none-eabi-newlib
from4.3.0
=>4.4.0
, I encounter a lot of linker issues, e.g., when building the example in #1146getentropy is not implemented
Also, there is a linker error related to
multiple definitions of sprintf
For now, downgrading
arm-none-eabi-newlib
to4.3
keeps things working...The text was updated successfully, but these errors were encountered: