Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <087f01bfd316$5e05c180$0100000a@dualbeast>
From: "Andy Hare" <ahare AT btinternet DOT com>
To: "Sourceware Mail List" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Problems building GDB and Insight-GDB under latest net release
Date: Sat, 10 Jun 2000 20:58:47 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600

Ok guys,

    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
build error

>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
>/c/cygnus/GNU-Source-Code/gdb/libiberty/strsignal.c:424: conflicting types
for `strsignal'
>/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../i686-pc-cygwin/include/s
tring.h:70: previous declaration of `strsignal'
>/c/cygnus/GNU-Source-Code/gdb/libiberty/strsignal.c: In function `psignal':
>/c/cygnus/GNU-Source-Code/gdb/libiberty/strsignal.c:597: warning:
comparison between signed and unsigned
>make[2]: *** [strsignal.o] Error 1
>make[2]: 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

Lines 68-73
>char *_EXFUN(strupr,(char *));
>#ifdef __CYGWIN32__
>const char    *_EXFUN(strsignal, (int __signo));
>int     _EXFUN(strtosigno, (const char *__name));
>#endif
>void  _EXFUN(swab,(const void *, void *, ssize_t));

Andy Hare


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com