RE: Silence pedantic warnings at header file level

--- Robert Collins <[EMAIL PROTECTED]> wrote: > Would this also fix the 'is not a prototype' error that cinstall > experiences? > > Rob > Compiling w32api/lib/test.c with gcc -I../include -Wall -Wstrict-prototypes -Wmissing-prototypes -pedantic test.c >err.log does not give that warning af

Re: RFC: Silence pedantic warnings at header file level

On Tue, Mar 05, 2002 at 09:44:14AM +1100, Danny Smith wrote: >GCC 3.x has a a new pragma that causes the rest of the code in >the current file to be treated as if it came from a system header > >Putting this right after the header guard of runtime and w32api headers >would silence all the "long lo

RE: Silence pedantic warnings at header file level

Would this also fix the 'is not a prototype' error that cinstall experiences? Rob > -Original Message- > From: Danny Smith [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 05, 2002 9:44 AM > To: cygwin-patches > Subject: RFC: Silence pedantic warnings at header file level > > > GCC 3

RFC: Silence pedantic warnings at header file level

GCC 3.x has a a new pragma that causes the rest of the code in the current file to be treated as if it came from a system header Putting this right after the header guard of runtime and w32api headers would silence all the "long long" and bitfield pedantic warnings that still occur. It would al

Terminal input processing fix (update)

Here a new version of my input processing patch. -- winsup/cygwin/ChangeLog -- 2002-03-04 Christian Lestrade <[EMAIL PROTECTED]> * include/sys/termios.h: define _POSIX_VDISABLE define CCEQ macro * fhandler_termios.cc: include (line_edit): Reco

Re: [PATCH] Use ftruncate64 directly to not lose upper 32 bits

On Mon, Mar 04, 2002 at 01:10:29PM +0800, Dmitry Timoshkov wrote: > Hello. > > 2002-03-04 Dmitry Timoshkov <[EMAIL PROTECTED]> > > * syscalls.cc (truncate64): Use ftruncate64 directly to not lose upper 32 bits. Thanks, applied. Corinna -- Corinna Vinschen Please, send mail