-
Notifications
You must be signed in to change notification settings - Fork 63
Saigo toolchain (first attempt) #971
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
Conversation
0cb7c20
to
d3198c9
Compare
What I get when building the cgame:
|
What I get when building the sgame:
And also:
|
And also that with sgame:
|
a8eacdc
to
a2d1b19
Compare
also avoid confusion with pnacl_finalize(dir, module, pnacl_arch, arch)
PNACl uses With Saigo, adding this C flag just prints that when compiling C files:
And then clang errors out on those errors when compiling C files. To say it otherwise, if I only do |
a56af8c
to
ccc789b
Compare
make sur zlib finds lseek() and read()
Adding |
I confirm Saigo do not ship |
Well, |
I managed to build the amd64 sgame with Saigo and run it:
Building cgame doesn't work because building RmlUi makes clang assert. |
d434029
to
a147a99
Compare
I can also build sgame for i686 but not arm one. |
So current status is:
Summary:
weird compilation errors:
Saigo clang segfaults when building RmlUi:
If we fix that it may work, as it happens in the very last step when linking |
About
Maybe I'm linking against amd64 |
No, it's more stupid than that, those We can't use them. We need to build |
Here is an example of compilation error happening when trying to build the sgame as arm nexe:
I guess the warning is wrong and is misinterpreting another error (like some type not being defined, or I don't know what else), but I don't get what is the real error I have to look for. |
Well, this one is even more mysterious:
|
More details:
|
This looks fishy: We have this in
|
Setting the right define helps in no way:
|
Hmmm, removing
|
I close this to reopen it with another branch name. |
Obsoleted by:
DO NOT MERGE THIS
This PR only exists because yesterday I toyed with the Saigo toolchain to change my mind, and then I thought I can still share the code, and we may have a dedicated thread if people want to talk about it.
It doesn't work.
How to use:
Get the Saigo toolchain, see:
Symlink the
native_client/toolchain/linux_x86/saigo_newlib
folder intoexternal_deps/linux-amd64-default_9
.Then do: