Sender: rich AT phekda DOT freeserve DOT co DOT uk Message-ID: <3F09E90D.FDF4A5E6@phekda.freeserve.co.uk> Date: Mon, 07 Jul 2003 22:41:33 +0100 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: djgpp-workers AT delorie DOT com Subject: Re: GCC3.3 & src\libc\go32\goqmem.c latest build failure References: <000701c34115$a67aa500$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: > In the changes that you did to src\libc\go32\goqmem.c a new function called > _go32_dpmi_get_free_memory_information was added, but this causes the file > to fail to build. This was not included in my patch for the file so I can > only assume that it was included from your file that you used to apply the > patch to before putting it in RCS. I am using a re-built GCC using the a > LIBC from two weekends ago. > > If I look in dpmi.h it re-defines the function as follows which I suspect > causes the problem. > #define _go32_dpmi_get_free_memory_information(x) > __dpmi_get_free_memory_information((__dpmi_free_mem_info *)(x)) > > I do not know why the function was added because I checked dpmi.h and it has > not chnaged since 2003/2/4 20:23:14 so I assume that this was included by > mistake. I will remove it from my build and see what happens. [snip] I had fixed some of the build with gcc 3.3 in the tree that I applied your patch to. Unfortunately some of my original fixes were still present. I did not mean to commit those. I've fixed goqmem.c now. It's checked in. Despite the message I got when I did the CVS commit (see mail a few days ago), it seems to have checked in. It's just the CVS mail notification that's broken. Sorry about that. Thanks, bye, Rich =] -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]