From: Bernard Pidoux <bernard.pidoux@upmc.fr>
To: Arjan van de Ven <arjan@infradead.org>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.31.1 BUG #include <asm/bitsperlong.h>
Date: Sun, 27 Sep 2009 19:35:59 +0200 [thread overview]
Message-ID: <4ABFA27F.1080100@upmc.fr> (raw)
In-Reply-To: <20090927151942.1c6a010a@infradead.org>
Here is the difference that made my system crazy :
--- /usr/src/linux-2.6.30.6/include/asm-generic/int-ll64.h 2009-06-10 05:05:27.000000000 +0200
+++ /usr/src/linux-2.6.31/include/asm-generic/int-ll64.h 2009-09-27 11:27:02.577804468 +0200
@@ -8,6 +8,8 @@
#ifndef _ASM_GENERIC_INT_LL64_H
#define _ASM_GENERIC_INT_LL64_H
+#include <asm/bitsperlong.h>
+
#ifndef __ASSEMBLY__
/*
* __xx is ok: it doesn't pollute the POSIX namespace. Use these in the
So, where are supposed to be the export routines that did not work ?
Bernard
> The correct fix is to include the missing bitsperlong in
> the asm-x86 directory.
> In other words your kernel headers are broken.
>
> Looking at latest kernel we do export bitsperlong.h.
> So see if you can find a fix for your broken kernel headers.
>
> Sam
next prev parent reply other threads:[~2009-09-27 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 11:36 Bernard Pidoux
2009-09-27 11:57 ` Bernard Pidoux
2009-09-27 12:44 ` Bernard Pidoux
2009-09-27 13:19 ` Arjan van de Ven
2009-09-27 16:29 ` Bernard Pidoux
2009-09-27 16:50 ` Arjan van de Ven
2009-09-27 17:35 ` Bernard Pidoux [this message]
2009-09-27 16:58 ` arnd
2009-09-27 18:33 ` Bernard Pidoux
-- strict thread matches above, loose matches on Subject: below --
2009-09-27 11:16 Bernard Pidoux
2009-09-27 11:24 ` Arjan van de Ven
2009-09-27 11:46 ` Sam Ravnborg
2009-09-27 9:56 Bernard Pidoux
2009-09-27 10:22 ` Sam Ravnborg
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=4ABFA27F.1080100@upmc.fr \
--to=bernard.pidoux@upmc.fr \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
Powered by JetHome