From: Jesper Juhl <jesper.juhl@gmail.com>
To: Steffen Weber <email@steffenweber.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Another compile problem with 2.6.15.5 on AMD64
Date: Thu, 2 Mar 2006 18:11:50 +0100 [thread overview]
Message-ID: <200603021811.50765.jesper.juhl@gmail.com> (raw)
In-Reply-To: <44071AF3.1010400@steffenweber.net>
On Thursday 02 March 2006 17:18, Steffen Weber wrote:
> I´m getting a compile error with 2.6.15.5 on x86_64 using GCC 3.4.4
> (does not seem to be related to the NFS one):
>
> CC mm/mempolicy.o
> mm/mempolicy.c: In function `get_nodes':
> mm/mempolicy.c:527: error: `BITS_PER_BYTE' undeclared (first use in
> this function)
> mm/mempolicy.c:527: error: (Each undeclared identifier is reported only
> once
> mm/mempolicy.c:527: error: for each function it appears in.)
>
Try the following (untested patch).
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---
mm/mempolicy.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.15.5/mm/mempolicy.c~ 2006-03-02 18:05:18.000000000 +0100
+++ linux-2.6.15.5/mm/mempolicy.c 2006-03-02 18:05:18.000000000 +0100
@@ -82,7 +82,7 @@
#include <linux/interrupt.h>
#include <linux/init.h>
#include <linux/compat.h>
-#include <linux/mempolicy.h>
+#include <linux/types.h>
#include <asm/tlbflush.h>
#include <asm/uaccess.h>
next prev parent reply other threads:[~2006-03-02 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 16:18 Another compile problem with 2.6.15.5 on AMD64 Steffen Weber
2006-03-02 17:11 ` Jesper Juhl [this message]
2006-03-02 17:29 ` Steffen Weber
2006-03-02 17:35 ` Jesper Juhl
2006-03-02 17:49 ` Steffen Weber
2006-03-02 17:59 ` Jesper Juhl
2006-03-02 18:07 ` Steffen Weber
2006-03-02 18:16 ` Jesper Juhl
2006-03-02 18:17 ` Andi Kleen
2006-03-02 18:23 ` Jesper Juhl
2006-03-02 19:15 ` Christoph Lameter
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=200603021811.50765.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=email@steffenweber.net \
--cc=linux-kernel@vger.kernel.org \
/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