-
Notifications
You must be signed in to change notification settings - Fork 69
Workarounds for Saigo Clang 21 #1878
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
base: master
Are you sure you want to change the base?
Conversation
cmake/DaemonFlags.cmake
Outdated
| endif() | ||
|
|
||
| try_c_cxx_flag(FPIC "-fPIC") | ||
| if (USE_NACL_SAIGO AND "${NACL_TARGET}" STREQUAL "armhf") |
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.
PIC is not useful with NaCl under any circumstances. Why not have the condition be simply NOT NACL?
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.
We can do that.
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.
Now done.
4f665b2 to
1a42cc6
Compare
|
I also imported the commit entirely removing GAME_PIE from: |
f350a60 to
e2971ec
Compare
|
Actually that For information, here is the Clang crash that happens with Google-built Saigo when building an amd64 cgame: It doesn't crash when building the amd64 sgame though. As noticed it crashes when building RmlUi, the build errors on arm also happen when building RmlUi. Google-built Saigo has enabled assertions, while self-built one doesn't, that may explain why I didn't get the compiler crash when using my self-built Saigo. That PIE code is likely incomplete for NaCl in Saigo to begin with, hence the |
e2971ec to
61b9bdd
Compare
Workarounds for latest Saigo
I need that when I build with the current Saigo (based on Clang 21).