Problems building GDB and Insight-GDB under latest net release
Sat Jun 10 12:58:00 GMT 2000
As some of you may know I have been building the GNU toolset for the ARM
processor using b20.1 each week after the regular snapshot release on
sourceware. Last week I updated to the latest net release of cygwin. I have
been trying to build both GDB and Insight-GDB and have got the following
>gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I/c/cygnus/GNU-Source-Code/gdb/libiberty
/../include -W -Wall ->Wtraditional
>/c/cygnus/GNU-Source-Code/gdb/libiberty/strsignal.c:424: conflicting types
tring.h:70: previous declaration of `strsignal'
>/c/cygnus/GNU-Source-Code/gdb/libiberty/strsignal.c: In function `psignal':
comparison between signed and unsigned
>make: *** [strsignal.o] Error 1
>make: Leaving directory `/build/gdb/libiberty'
This occurs in both Insight and GDB. I have looked at the code in question
and found that the definitions in string.h differ to the definitions in
strsignal.c. In strsignal.c the function strsignal is defined as a const
char * but the string.h shows it as a char *. Modifying string.h to const
char * now allows the stuff to compile. My problem is, should the mods be
done in string.h or should strstring.c be changed, and thus who needs to
know of the problem, here or in the GDB lists ?
The code changes for string.h are shown below
>char *_EXFUN(strupr,(char *));
>const char *_EXFUN(strsignal, (int __signo));
>int _EXFUN(strtosigno, (const char *__name));
>void _EXFUN(swab,(const void *, void *, ssize_t));
Want to unsubscribe from this list?
Send a message to email@example.com
More information about the Cygwin