-
Notifications
You must be signed in to change notification settings - Fork 318
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
Errors building 1.0.0 for multiple architectures #938
Comments
Hi, this seems to be something like andrew-d/rough-auditing-tool-for-security#9, where the checker/warning doesn't understand the inttypes.h mechanism (a macro that expands to the actual format string). Regrettable though it is, looks like the best option might be to disable -Wformat-extra-args and -Wformat= for gcc builds? |
Unfortunately passing
|
hm, this is difficult to understand. I've double-checked the PRIi64 documentation and that we are including inttypes.h. I suspect that
One unlikely idea: does it help to change the include to |
Hmm, Comparing
I can find a GCC header file that redefines
Oh, and I don't have any |
Building a simple hello world appears to work,
|
Ah, nice idea to diff the headers. I think defining __STDC_FORMAT_MACROS would solve this. See also WAVM/WAVM#266. |
On some systems this requires a macro to be set. Where feasible, replace int-sized printf args with static_cast<int>. PiperOrigin-RevId: 469698041
On some systems this requires a macro to be set. Where feasible, replace int-sized printf args with static_cast<int>. PiperOrigin-RevId: 469698041
On some systems this requires a macro to be set. Where feasible, replace int-sized printf args with static_cast<int>. PiperOrigin-RevId: 469698041
On some systems this requires a macro to be set. Where feasible, replace int-sized printf args with static_cast<int>. PiperOrigin-RevId: 469698041
On some systems this requires a macro to be set. Where feasible, replace int-sized printf args with static_cast<int>. PiperOrigin-RevId: 469698041
1.0.1 builds like a charm on every architecture, thank you very much! |
Thanks for letting us know :) |
Hi guys, I'm trying to cross-compile highway for a lot of achitectures, but I'm running into a lot of seemingly "missing" parentheses, which seems odd because it builds just fine for half of them already. Using mostly crosstool-ng toolchains for all of them, GCC 10, but also mingw for windows and ndk for android. Having troubles with linux armv5, armv7, ppc32 and x86 targets, below is the full log, same error for all of them: https://paste.xinu.at/ZEKmexD183AkbI72/
Any ideas?
The text was updated successfully, but these errors were encountered: