All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: NX related build failure in latest pv_ops dom0 hackery tree
Date: Thu, 23 Apr 2009 14:01:24 +0200	[thread overview]
Message-ID: <1240488084.6074.2.camel@marc> (raw)
In-Reply-To: <49E75E06.1060702@goop.org>

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

  parent reply	other threads:[~2009-04-23 12:01 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 19:23 NX related build failure in latest pv_ops dom0 hackery tree Pasi Kärkkäinen
2009-04-05  5:25 ` Jeremy Fitzhardinge
2009-04-12 16:55   ` Christophe Saout
2009-04-12 18:57     ` Boris Derzhavets
2009-04-12 20:06       ` Boris Derzhavets
2009-04-12 20:14         ` Christophe Saout
2009-04-13 10:18     ` Pasi Kärkkäinen
2009-04-13 12:08       ` Boris Derzhavets
2009-04-13 13:28       ` Andrew Lyon
2009-04-13 15:34         ` Boris Derzhavets
2009-04-13 18:20     ` Jeremy Fitzhardinge
2009-04-14 16:53     ` Jeremy Fitzhardinge
2009-04-14 17:11       ` Thomas DuBuisson
2009-04-14 19:58         ` Jeremy Fitzhardinge
2009-04-14 20:30           ` Thomas DuBuisson
2009-04-14 21:03             ` Jeremy Fitzhardinge
2009-04-15  7:01             ` Pasi Kärkkäinen
2009-04-15 16:08               ` Jeremy Fitzhardinge
2009-04-15 16:55                 ` Thomas DuBuisson
2009-04-15 18:36                   ` Thomas DuBuisson
2009-04-14 17:31       ` Boris Derzhavets
2009-04-14 18:00       ` Boris Derzhavets
2009-04-14 21:43       ` Christophe Saout
2009-04-16 13:16       ` Christophe Saout
2009-04-16 16:13         ` Jeremy Fitzhardinge
2009-04-16 16:24           ` Christophe Saout
2009-04-16 16:34             ` Jeremy Fitzhardinge
2009-04-16 16:49               ` Christophe Saout
2009-04-23 12:01               ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ] [this message]
2009-04-23 17:06                 ` Jeremy Fitzhardinge
2009-04-16 16:34             ` Jeremy Fitzhardinge
2009-04-16 22:05           ` Christophe Saout
2009-04-16 22:27             ` Jeremy Fitzhardinge
2009-04-16 23:45               ` Christophe Saout
2009-04-16 23:54                 ` Jeremy Fitzhardinge
2009-04-16 23:54                 ` Christophe Saout
2009-04-17  0:03                   ` Jeremy Fitzhardinge
2009-04-17  0:34                     ` Christophe Saout
2009-04-17  0:49                       ` Jeremy Fitzhardinge
2009-04-17 12:17                         ` Christophe Saout
2009-04-17 12:41                         ` Christophe Saout
2009-04-17 13:58                           ` Jeremy Fitzhardinge
2009-04-17  0:03                   ` Mainline kernel dom0 support Valtteri Kiviniemi
2009-04-18 16:44                     ` Thiago Camargo Martins Cordeiro
2009-04-18 17:26                       ` Thiago Camargo Martins Cordeiro
2009-04-18 20:39                       ` Boris Derzhavets
2009-04-19 19:25                         ` M A Young

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1240488084.6074.2.camel@marc \
    --to=mad@wol.de \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.