public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:59:29 +0100	[thread overview]
Message-ID: <200603021859.29728.jesper.juhl@gmail.com> (raw)
In-Reply-To: <44073037.2090709@steffenweber.net>

On Thursday 02 March 2006 18:49, Steffen Weber wrote:
> Jesper Juhl wrote:
> > On 3/2/06, Steffen Weber <email@steffenweber.net> wrote:
> >> Jesper Juhl wrote:
> >>> 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).
> >> Thanks for your reply, but this patch does not solve the problem (same
> >> error message). I´ve appended my .config in case that might help.
> >>
> > 
> > Hmm, types.h contains the
> > 
> > #define BITS_PER_BYTE 8
> > 
> > that mmpolicy.c needs, so including that header should do the trick... odd..
> > I'll look at the code a bit more.
> There is no BITS_PER_BYTE in include/types.h. I´ve grepped through the 
> kernel source (2.6.15 and 2.6.15.5) and found that BITS_PER_BYTE is 
> defined only in arch/i386/mach-voyager/voyager_cat.c
> 

Whoops, I was looking here : http://sosdg.org/~coywolf/lxr/source/include/linux/types.h#L11

Try this patch instead : 



Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---

 arch/i386/mach-voyager/voyager_cat.c |    1 -
 include/linux/types.h                |    2 ++
 mm/mempolicy.c                       |    2 +-
 3 files changed, 3 insertions(+), 2 deletions(-)

--- 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>
 
--- linux-2.6.15.5/arch/i386/mach-voyager/voyager_cat.c~	2006-03-02 18:55:47.000000000 +0100
+++ linux-2.6.15.5/arch/i386/mach-voyager/voyager_cat.c	2006-03-02 18:55:47.000000000 +0100
@@ -114,7 +114,6 @@ static struct resource qic_res = {
  * It writes num_bits of the data buffer in msg starting at start_bit.
  * Note: This function assumes that any unused bit in the data stream
  * is set to zero so that the ors will work correctly */
-#define BITS_PER_BYTE 8
 static void
 cat_pack(__u8 *msg, const __u16 start_bit, __u8 *data, const __u16 num_bits)
 {
--- linux-2.6.15.5/include/linux/types.h~	2006-03-02 18:54:57.000000000 +0100
+++ linux-2.6.15.5/include/linux/types.h	2006-03-02 18:54:57.000000000 +0100
@@ -8,6 +8,8 @@
 	(((bits)+BITS_PER_LONG-1)/BITS_PER_LONG)
 #define DECLARE_BITMAP(name,bits) \
 	unsigned long name[BITS_TO_LONGS(bits)]
+
+#define BITS_PER_BYTE 8
 #endif
 
 #include <linux/posix_types.h>




  reply	other threads:[~2006-03-02 17:59 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
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 [this message]
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=200603021859.29728.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