-
Notifications
You must be signed in to change notification settings - Fork 67
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
Error building libc for Cross ARM Cortex-M4F #194
Comments
Looks like a behavioral change in Meson is causing CMocka to fail to cross-compile (previously, it was not being compiled). Working on a fork of the build rules for that project, and then will adjust this repo to use the forked version. |
Would there be a quick workaround to disable the cmocka cross build ? |
Just completed the changes and pushed to the repo if you want to give that a try. |
Thanks for the quick response, libc seems to have completed. I will start on the stdc++ libs now. I had an additional error earlier in test/meson.build at line 156 which I had to change to |
Do you recall the error? Was that in the skeleton? |
Output from make.....
|
I'm attempting to compile libc for an STM32L4R5 (Cortex-M4F) on a Linux system running kubuntu 22.04
I cloned the latest libc from the GitHub repo.
I am completely new to using the meson build system, but am willing to learn.
Any help would be appreciated.
After cloning the libc repo...
It seems to fail trying to compile cmocka for the ARM STM32 complaining about a missing setjmp.h which I assume should be provided by the local libc headers not the system. setjmp.h is in the libc/include directory.
The compiler invocation to compile cmocka.c does not include any reference to the local header files.
Is there a simple way to add the local libc headers to the cmocka.c build command ljne ?
The complete meson-log.txt file is attached here, but I don't see any reference to cmocka.c there so I'm not sure how helpful that will be.
Here is the final line of output from the build attempt
meson-log.txt
The text was updated successfully, but these errors were encountered: