Dennis Ruffer wrote: > > Anton, > > On Jaguar (10.2.1), your changes produce the following errors: > > signals.c: In function `bsd_signal': > signals.c:77: `SA_ONSTACK' undeclared (first use in this function) > signals.c:77: (Each undeclared identifier is reported only once > signals.c:77: for each function it appears in.) > signals.c: In function `install_signal_handlers': > signals.c:359: `stack_t' undeclared (first use in this function) > signals.c:359: parse error before `sigstack' > signals.c:362: `sigstack' undeclared (first use in this function) > signals.c:362: `SIGSTKSZ' undeclared (first use in this function) > signals.c:365: warning: implicit declaration of function `sigaltstack' > signals.c:365: parse error before `)' > > DaR
Thanks. Jaguar is a codename for some MacOS X version, right? Looks like there's no sigaltstack() and friends there (nor SA_SIGINFO). I expected this from older Unices, but had hoped that this functionality would be present in all recent systems (after all, it's in Unix 95). Try putting #define _XOPEN_SOURCE 500 #define _XOPEN_SOURCE_EXTENDED #define _POSIX_C_SOURCE 199506L at the start of engine/signals.c and recompile. Let me know if this works or if you find another way to get to sigaltstack(). If not, you will just have to eliminate this stuff and live with this minor unpleasantness (the absensence of SA_SIGINFO causes much more unpleasantness, though: "Invalid memory address" instead of "Stack underflow" etc.). - anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
