-
Notifications
You must be signed in to change notification settings - Fork 2k
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
build system: fix compilation with LLVM [backport 2022.10] #18928
build system: fix compilation with LLVM [backport 2022.10] #18928
Conversation
GCC on some platforms does need an executable stack to generate trampoline code, but use of nested functions is not allowed in RIOT's code base anyway. (cherry picked from commit 67ba1a0)
The test for the requirement of disabling wchar_t size warnings assumed that $(CC) is used for linking, instead of $(LINK). With GCC $(LINK) and $(CC) happen to be (in most cases) identical, but with LLVM they are not. This results in issues with compiling with LLVM. (cherry picked from commit 0077e9a)
Murdock results✔️ PASSED 158f52d makefiles/libc: fix wchar_t size warnings on LLVM
ArtifactsThis only reflects a subset of all builds from https://ci-prod.riot-os.org. Please refer to https://ci.riot-os.org for a complete build for now. |
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.
ACK
Hmmm... A bit late it seems 😕 |
Or it just merged as soon as the ack... Cool. |
Yes. I enablee auto merge and the ACK was the last checkbox to tick :) |
Thx :) |
Backport of #18845
Contribution description
-z noexecstack
to link flags$(CC)
is used for linking, instead of$(LINK)
. With GCC$(LINK)
and$(CC)
happen to be (in most cases) identical, but with LLVM they are not. This results in issues with compiling with LLVM.Testing procedure
No change in binaries and everything should still compile.
Issues/PRs references
Inspired by #18844