Re: Problem when cross-compiling trunk in libgcc2.c

2009-03-19 Thread Ozkan Sezer
On Thu, Mar 19, 2009 at 8:25 PM, Kai Tietz wrote: > 2009/3/19 Ozkan Sezer : >> On Thu, Mar 19, 2009 at 8:04 PM, Vincent R. wrote: >>> On Thu, 19 Mar 2009 19:58:13 +0200, Ozkan Sezer wrote: I'm a bit amazed that the prototype for VirtualProtect() is known to the compiler but the definit

Re: Problem when cross-compiling trunk in libgcc2.c

2009-03-19 Thread Kai Tietz
2009/3/19 Ozkan Sezer : > On Thu, Mar 19, 2009 at 8:04 PM, Vincent R. wrote: >> On Thu, 19 Mar 2009 19:58:13 +0200, Ozkan Sezer wrote: >>> I'm a bit amazed that the prototype for VirtualProtect() is known to the >>> compiler but the definition of DWORD is not.. In any case, it should be >>> fixed

Re: Problem when cross-compiling trunk in libgcc2.c

2009-03-19 Thread Dave Korn
Ozkan Sezer wrote: > On Thu, Mar 19, 2009 at 8:04 PM, Vincent R. wrote: >> However you are wrong about DWORD definition it has always be defined >> like this : >> >> typedef unsigned long DWORD, *PDWORD, *LPDWORD; >> >> at least windows. >> > > A DWORD on windows is an unsigned 32 bit integer, t

Re: Problem when cross-compiling trunk in libgcc2.c

2009-03-19 Thread Ozkan Sezer
On Thu, Mar 19, 2009 at 8:04 PM, Vincent R. wrote: > On Thu, 19 Mar 2009 19:58:13 +0200, Ozkan Sezer wrote: >> I'm a bit amazed that the prototype for VirtualProtect() is known to the >> compiler but the definition of DWORD is not.. In any case, it should be >> fixed easily by changing DWORD into

Re: Problem when cross-compiling trunk in libgcc2.c

2009-03-19 Thread Vincent R.
On Thu, 19 Mar 2009 19:58:13 +0200, Ozkan Sezer wrote: > I'm a bit amazed that the prototype for VirtualProtect() is known to the > compiler but the definition of DWORD is not.. In any case, it should be > fixed easily by changing DWORD into unsigned int which is what a > DWORD is always defined a

Re: Problem when cross-compiling trunk in libgcc2.c

2009-03-19 Thread Ozkan Sezer
I'm a bit amazed that the prototype for VirtualProtect() is known to the compiler but the definition of DWORD is not.. In any case, it should be fixed easily by changing DWORD into unsigned int which is what a DWORD is always defined as. And PR 39063 is still open anyway. -- Ozkan

Re: Problem when cross-compiling trunk in libgcc2.c

2009-03-19 Thread H.J. Lu
On Thu, Mar 19, 2009 at 7:49 AM, Vincent R. wrote: > Hi, > > I tried to generate a cross-compiler from trunk a few hours ago and I have > noticed that > libgcc2.c doesn't compile anymore because of the following function : It is caused by: http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00822.html