Ah yes i have forgotten to report another problem with rts.{h,c} in rts.h if HAVE_STRSIGNAL is defined it does declare the function char *strsignal( int ) witch conflicts with the strsignal definition in the cygwin include file string.h const char *_EXFUN(strsignal, (int __signo)); => compiler abort If we have defined HAVE_STRSIGNAL does it mean we have a strsignal function defined in string.h or does it only mean the lib has one ? In any case you can put a #ifndef __CYGWIN__ around the strsignal definition in rts.h
On 25 Jul 00, at 0:02, Joachim Falk wrote:
Ah yes i have forgotten to report another problem with rts.{h,c} in rts.h if HAVE_STRSIGNAL is defined it does declare the function char *strsignal( int ) witch conflicts with the strsignal definition in the cygwin include file string.h const char *_EXFUN(strsignal, (int __signo)); => compiler abort
Funny - I have never experienced this problem, and I have been compiling GPC under Cygwin since last summer.
If we have defined HAVE_STRSIGNAL does it mean we have a strsignal function defined in string.h or does it only mean the lib has one ?
AFAICS it means that it is defined in one of the standard headers.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro v5.22.1 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm Email: African_Chief@bigfoot.com
-
Joachim Falk -
Prof Abimbola A Olowofoyeku