From: Andi Kleen <ak@muc.de>
To: "R. J. Wysocki" <rjwysocki@sisk.pl>
Cc: Andrew Morton <akpm@zip.com.au>, Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-rc3-mm2 does not build on AMD64 + essential patch is missing
Date: 6 May 2004 09:43:02 +0200 [thread overview]
Date: Thu, 6 May 2004 09:43:02 +0200 [thread overview]
Message-ID: <20040506074302.GA47323@colin2.muc.de> (raw)
In-Reply-To: <200405052210.18074.rjwysocki@sisk.pl>
On Wed, May 05, 2004 at 10:13:52PM +0200, R. J. Wysocki wrote:
> Hi,
>
> The 2.6.6-rc3-mm2 kernel does not buld on AMD64 w/ NUMA, it appears. Here's
> what the gcc says:
>
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> arch/x86_64/ia32/built-in.o(.text+0xa164): In function `ia32_setup_arg_pages':
> : undefined reference to `mpol_set_vma_default'
> kernel/built-in.o(.text+0x9ba0): In function `do_exit':
> : undefined reference to `mpol_free'
> make: *** [.tmp_vmlinux1] Error 1
>
> (attached is the .config). Also, IMHO, the patch:
Just revert the broken small-numa-api-fixups.patch patch,
which never seems to have been compile tested on anything.
>
> --- include/asm-x86_64/processor.h.orig 2004-05-05 21:35:55.890656408 +0200
> +++ include/asm-x86_64/processor.h 2004-05-05 21:41:15.930003032 +0200
> @@ -20,6 +20,8 @@
> #include <asm/mmsegment.h>
> #include <linux/personality.h>
>
> +#define ARCH_MIN_TASKALIGN 16
> +
> #define TF_MASK 0x00000100
> #define IF_MASK 0x00000200
> #define IOPL_MASK 0x00003000
>
> should be applied to it, so that it does not crash at init.
AFAIK Andrew fixed this in a different way.
-Andi
next prev parent reply other threads:[~2004-05-06 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 20:13 R. J. Wysocki
2004-05-05 20:58 ` Andrew Morton
2004-05-06 19:38 ` R. J. Wysocki
2004-05-06 7:43 ` Andi Kleen [this message]
2004-05-06 7:47 ` Christoph Hellwig
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=20040506074302.GA47323@colin2.muc.de \
--to=ak@muc.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rjwysocki@sisk.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®