PAE Build Break

PAE Build Break

[David F Barrera]

Bugzilla Bug 389 - PAE build break- mm.c:3250: error: parse error before 
numeric constant
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=389

changeset:   7695:6e2225934d84
tag:         tip
parent:      7683:a5195bf5671d
parent:      7694:f544934dd0b6
user:        Michael.Fetterman@cl.cam.ac.uk
date:        Tue Nov  8 07:41:25 2005 +0100
summary:     merge

gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix 
include -Wall -Werror -Wno-pointer-arith -pipe 
-I/tmp/xen-unstable.hg/xen/include 
-I/tmp/xen-unstable.hg/xen/include/asm-x86/mach-generic 
-I/tmp/xen-unstable.hg/xen/include/asm-x86/mach-default -msoft-float 
-m32 -march=i686 -DCONFIG_X86_PAE=1 -g -DVERBOSE -c mm.c -o mm.o
mm.c: In function `ptwr_do_page_fault':
mm.c:3250: error: parse error before numeric constant
mm.c:3255: error: `endif' undeclared (first use in this function)
mm.c:3255: error: (Each undeclared identifier is reported only once
mm.c:3255: error: for each function it appears in.)
make[3]: *** [mm.o] Error 1
make[3]: Leaving directory `/tmp/xen-unstable.hg/xen/arch/x86'
make[2]: *** [/tmp/xen-unstable.hg/xen/xen] Error 2
make[2]: Leaving directory `/tmp/xen-unstable.hg/xen'
make[1]: *** [install-xen] Error 2

Re: PAE Build Break

[Keir Fraser]

On 8 Nov 2005, at 16:06, David F Barrera wrote:

> Bugzilla Bug 389 - PAE build break- mm.c:3250: error: parse error 
> before numeric constant
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=389

I think maybe your tree is corrupted. PAE builds fine for me and the 
compile error makes no sense when I look at the code.

  -- Keir

Re: PAE Build Break

[David F Barrera]

Keir Fraser wrote:

>
> On 8 Nov 2005, at 16:06, David F Barrera wrote:
>
>> Bugzilla Bug 389 - PAE build break- mm.c:3250: error: parse error 
>> before numeric constant
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=389
>
>
> I think maybe your tree is corrupted. PAE builds fine for me and the 
> compile error makes no sense when I look at the code.

You are correct. Even though the tree correctly showed the last 
changeset on the history, it was corrupt. Also, the update (hg pull -u) 
had gone smoothly, so I did not suspect the tree being corrupt.

>
>  -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>