This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: [RFA] patch to solve libiberty strsignal changes (plus a minor cross-compilation fix)
- To: Andrew Cagney <ac131313 at cygnus dot com>, gdb-patches at sourceware dot cygnus dot com
- Subject: Re: [RFA] patch to solve libiberty strsignal changes (plus a minor cross-compilation fix)
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Sat, 3 Jun 2000 00:40:37 -0400
- References: <20000531182910.A29100@cygnus.com> <200006010604.CAA09992@indy.delorie.com> <20000601021247.A13381@cygnus.com> <20000601222133.A20052@cygnus.com> <393724EA.2C034823@cygnus.com> <20000602112110.A1020@cygnus.com>
On Fri, Jun 02, 2000 at 11:21:10AM -0400, Chris Faylor wrote:
>On Fri, Jun 02, 2000 at 01:07:22PM +1000, Andrew Cagney wrote:
>>> Thu Jun 1 22:11:19 2000 Christopher Faylor <cgf@cygnus.com>
>>>
>>> * configure.in: Check for declaration of strsignal in string{,s}.h.
>>> Detect correct versions of ranlib and windres when cross-compiling.
>>> * configure: Regenerate.
>>> * config.in: Define NEED_DECLARATION_STRSIGNAL if strsignal is not
>>> declared in system header file.
>>> * defs.h: Move strsignal declaration into gdb_string.h.
>>> * gdb_string.h: Declare strsignal here if if isn't declared anywhere
>>> else.
>>
>>I'm fairly sure that GDB simply shouldn't be calling strsignal().
>>lowcore.c should use the target signal to string function while the
>>others are going to be made obsolete.
>
>Ok. That doesn't help much with my current problem, though. How do I
>build a Windows version of gdb? I don't think you want me to be making
>changes to places like lowcore.c. I'm really not qualified for that...
FWIW, I've worked around this problem in newlib with a truly awful hack.
That will at least fend off problems from cygwin users who try to build gdb.
cgf