Re: [Xen-devel] Re: NX related build failure in latest pv_ops dom0 hackery tree

["Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@xxxxxx>]

Hello Jeremy,


did a fresh clone of your repo and got some warning from git:

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
linux-2.6-xen
Initialized empty Git repository in linux-2.6-xen2/.git/
remote: Counting objects: 1294968, done.
remote: Compressing objects: 100% (225881/225881), done.
remote: Total 1294968 (delta 1084032), reused 1271909 (delta 1061619)
Receiving objects: 100% (1294968/1294968), 306.19 MiB | 671 KiB/s, done.
Resolving deltas: 100% (1084032/1084032), done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.

something broken here?

The chechout worked:
$ cd linux-2.6-xen
$ git checkout origin/xen-tip/next -b xen-tip/next
warning: You appear to be on a branch yet to be born.
warning: Forcing checkout of origin/xen-tip/next.
Checking out files: 100% (27906/27906), done.
Branch xen-tip/next set up to track remote branch
refs/remotes/origin/xen-tip/next.
Switched to a new branch "xen-tip/next"


But this time, it doesn't build without CONFIG_NUMA.
This is a i686 PAE build.
Didn't test tip itself for presence of this error:

$ make
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf -s arch/x86/Kconfig
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  CHK     include/linux/utsrelease.h
  UPD     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86
  CC      kernel/bounds.s
  GEN     include/linux/bounds.h
  CC      arch/x86/kernel/asm-offsets.s
In file included from include/linux/suspend.h:8,
                 from arch/x86/kernel/asm-offsets_32.c:11,
                 from arch/x86/kernel/asm-offsets.c:2:
include/linux/mm.h:495:2: error: #error SECTIONS_WIDTH+NODES_WIDTH
+ZONES_WIDTH > BITS_PER_LONG - NR_PAGEFLAGS
make[1]: *** [arch/x86/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2

Am Donnerstag, den 16.04.2009, 09:34 -0700 schrieb Jeremy Fitzhardinge:
> 
> Actually, the kernel to test is xen-tip/next.  That's going to be the 
> base for ongoing development, and I'll cull all the rest of the branches 
> once all their nutritious changesets have been extracted.  Oh, and it 
> actually works.
> 
>     J


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