On 2013-06-17 11:21, Thorsten Glaser wrote:
Jens Staal dixit:
I picked up 2 problems immediately, which was that ape/cc does not understand
-O2 and -W... stuff. Because of this I will add a small test under compiler
You can export stuff like HAVE_CAN_OTWO=0 before running Build.sh
or put that into the Plan9) case.
For some strange reason ape/cc also chokes on this:
char ctasserts_dblcheck[sizeof(struct ctasserts) == NUM ? 1 : -1];
Working around the assertions is, unfortunately, not permitted.
Apparently, by passing -L to Build.sh, ape/cc can build without a
workaround. Does this mean that I should try to put in a test for
"unknown" compiler on Plan9 early in the script and trigger "legacy"?
The gcc port on Plan9 can build without any modifications to Build.sh
(except the re-definitions for seteuid and setegid).
