Sender: rich AT phekda DOT freeserve DOT co DOT uk Message-ID: <3E1B211B.61F92F6C@phekda.freeserve.co.uk> Date: Tue, 07 Jan 2003 18:48:59 +0000 From: Richard Dawe X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586) X-Accept-Language: de,fr MIME-Version: 1.0 To: Andrew Cottrell CC: DJGPP workers Subject: Re: Make realloc pointer problem [was part of Re: GCC 3.2.1 build failure] References: <006101c2b636$00763030$0100a8c0 AT acp42g> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hello. Andrew Cottrell wrote: > I checked the past postings and this one slipped between the cracks. In the > last posting of the previous thread you asked for me to give more details > which I am now doing 7 months late..... [snip] > > make.exe[2]: Entering directory `d:/dj204/gnu/make-3.80/glob' > > gcc -I.. -I. -I. -I./glob -DHAVE_CONFIG_H -O2 -g -c fnmatch.c > > gcc -I.. -I. -I. -I./glob -DHAVE_CONFIG_H -O2 -g -c glob.c > > In file included from glob.c:813: > > glob.c: In function `glob': > > glob.c:197: warning: passing arg 0 of `my_realloc' from incompatible > > pointer type > > > > Arg 0? I still don't understand what arg 0 is. Which version of gcc is that with? gcc 3.2.1? Does it occur when you build against DJGPP 2.03? > This also occurs with make 3.79.2a1, which is where I first seen the problem > and it is also in 3.80. > > Should I report this to the make maintainers or is it a DJGPP specific > problem or should I just ignore this warning? This doesn't look like a DJGPP-specific problem to me. If you get the same error building against DJGPP 2.03, I'd report it to the maintainers. > glob.c line 184: > #ifndef __GNU_LIBRARY__ > # ifdef __GNUC__ > __inline > # endif > # ifndef __SASC > # ifdef WINDOWS32 [snip] Are any of these defined? __GNUC__ presumably is. WINDOWS32? Bye, Rich =] -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]