From: Steffen Weber <email@steffenweber.net>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Another compile problem with 2.6.15.5 on AMD64
Date: Thu, 02 Mar 2006 18:49:43 +0100 [thread overview]
Message-ID: <44073037.2090709@steffenweber.net> (raw)
In-Reply-To: <9a8748490603020935h4936ae0eob4bcf107cc75c923@mail.gmail.com>
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
Steffen
next prev parent reply other threads:[~2006-03-02 17:49 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 [this message]
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=44073037.2090709@steffenweber.net \
--to=email@steffenweber.net \
--cc=jesper.juhl@gmail.com \
--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