I looked somewhat further and found out the curious fact that on
MacOSX 10.5.x both /usr/include/signal.h and /usr/include/sys/signal.h
exist!
The first one does not include the second one, neither does one of the
includes:
#ifndef _USER_SIGNAL_H
#define _USER_SIGNAL_H
#include sys/cdefs.h
Hans van der Meer wrote:
I looked somewhat further and found out the curious fact that on
MacOSX 10.5.x both /usr/include/signal.h and /usr/include/sys/signal.h
exist!
That is normal, signals have a portable interface, as defined in
ISO C99. That is the interface provided in
2007/12/20, Hans van der Meer [EMAIL PROTECTED]:
Probably changing the code into:
#include signal.h
#ifndef _SIGNAL_H_
#include sys/signal.h
#endif
might help, but I have not tested this (some of the pie should be left
for Taco c.s. ;-)
Just curious: What does the man page of signal.h say
Hi guys,
On Fri, 21 Dec 2007 03:50:04 -0700, Martin Schröder [EMAIL PROTECTED]
wrote:
2007/12/20, Hans van der Meer [EMAIL PROTECTED]:
Probably changing the code into:
#include signal.h
#ifndef _SIGNAL_H_
#include sys/signal.h
#endif
might help, but I have not tested this (some of the
Idris Samawi Hamid wrote:
Hi guys,
On Fri, 21 Dec 2007 03:50:04 -0700, Martin Schröder [EMAIL PROTECTED]
wrote:
2007/12/20, Hans van der Meer [EMAIL PROTECTED]:
Probably changing the code into:
#include signal.h
#ifndef _SIGNAL_H_
#include sys/signal.h
#endif
might help, but I
Should'nt this discssion go to the dev-luatex list? :-)
I think no, at least not now.
Luatex is actually very 'tangled' with context mkiv and context users .
--
luigi
http://wiki.contextgarden.net/User:Luigi.scarso/Merry_Christmas_2007
it's new .
it's powerful .
it's luatex .
