Message-ID: <B0000065212@stargate.astr.lu.lv>
From: "Andris Pavenis" <pavenis AT lanet DOT lv>
To: Frank Donahoe <fdonahoe AT wilkes1 DOT wilkes DOT edu>
Date: Wed, 20 Jan 1999 17:10:24 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Will gcc 2.8.1 compile itself under DJGPP 2.02?
CC: djgpp AT delorie DOT com
References: <B0000064264 AT stargate DOT astr DOT lu DOT lv>
In-reply-to: <Pine.A32.3.96.990120085150.5065B-100000@wilkes1.wilkes.edu>
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp AT delorie DOT com

On 20 Jan 99, at 9:30, Frank Donahoe wrote:

> > 
> It is one thing to ignore them when compiling the compiler with the
> warning flags "-W" and "-Wall" raised  but: !!
> 
> I thought the rebuilding under v2.02 was completed when the size of
> the installed executables stabilized.  However, when the new "gcc"
> is used to build another program, in this case infozip's zip 2.3k
> screen after screen of similar warnings are issued even without the
> warning flags raised.  See below.  Since the released binaries do
> not behave this way there is something which has gone wrong in the
> build.  These warnings cannot be ignored.  If allowed to continue
> it could undermine the faith of a whole generation of programmers
> in the orthogonality of the standard header files.
> 
> ; - - - - begin zip-err.281
> In file included from tailor.h:116,
>                  from zip.h:21,
>                  from zip.c:18:
> c:/djg/lib/gcc-lib/djgpp/2.81/include/stddef.h:168: warning: redefinition
> of `size_t'
> c:/djg/lib/gcc-lib/djgpp/2.81/include/sys/types.h:30: warning: `size_t'
>  previously declared here
> In file included from tailor.h:120,
>                  from zip.h:21,
>                  from zip.c:18:

I know this. You should look which include files are in 
lib/gcc-lib/djgpp/2.81/include from binary archives of gcc-2.8.1 
(gcc281b.zip, gpp281b.zip, objc281b.zip, g770523b.zip and remove 
other files manually from this directory). 

Of course one can try to fix  fixinc.djgpp  script to avoid this warning messages
but currently I'm not going to do that. One of the way how one can do that is
to replace fixinc script with empty one and add actual fixes we need for DJGPP.

Andris