Hi Frank
I am building the snapshot at the moment for Mingw (gcc-2.93-8). The build process halted with errors relating to undefined "sys_siglist" in gpc.c. I checked up on this, and had to comment out the declaration below: "#define strsignal(N) (sys_siglist[(N)])"
Under Mingw strsignal() is defined in libiberty.h,
In gcc-2.95.3 (I assume your 2.93 was a typo)
It was. I was referring to gcc-2.95.3-8 (Mingw special)
the declaration in libiberty is commented out. Does Mingw use some special patches to libiberty.h?
Sorry - I actually found that they are commented out as well (I used "grep" before, but this time I opened the file and looked inside it).
If so, what do they look like? If they `#define strsignal', it should be enough to put an `#ifndef strsignal' around the definition in gpc.c. Or does it provide an external declaration?
It is commented out, as follows:
/*extern const char *strsignal PARAMS ((int));*/
/* Return the name of a signal number (e.g., strsigno (SIGHUP) returns "SIGHUP"). */
extern const char *strsigno PARAMS ((int));
/* Given the name of a signal, return its number. */
extern int strtosigno PARAMS ((const char *));
But it strsignal exists in libiberty.a, and the patch that you sent works.
but it seems that the configure script doesn't look there.
I suppose not. Since libiberty.h is distributed with gcc, it can assume it knows what's in there.
There is a copy in "/mingw/include/" (the system include directory). Should it not be there?
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~african_chief/