Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Sat, 10 Jun 2000 16:04:30 -0400 To: Sourceware Mail List Cc: ahare AT btinternet DOT com Subject: Re: Problems building GDB and Insight-GDB under latest net release Message-ID: <20000610160430.A1373@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: Sourceware Mail List , ahare AT btinternet DOT com References: <087f01bfd316$5e05c180$0100000a AT dualbeast> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <087f01bfd316$5e05c180$0100000a@dualbeast>; from ahare@btinternet.com on Sat, Jun 10, 2000 at 08:58:47PM +0100 On Sat, Jun 10, 2000 at 08:58:47PM +0100, Andy Hare wrote: >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)); This is already a "const" in sourceware version of newlib, from whence this file comes, and in the newest cygwin DLL net release. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com