From: Bernard Pidoux <bernard.pidoux@upmc.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.31.1 BUG #include <asm/bitsperlong.h>
Date: Sun, 27 Sep 2009 13:57:28 +0200 [thread overview]
Message-ID: <4ABF5328.8020901@upmc.fr> (raw)
In-Reply-To: <4ABF4E36.4090703@upmc.fr>
The only file in asm-x86 directory is asm-offsets.h
This is a Mandriva 2009.1 Spring distro.
I checked that it was the same on two other machines with the same
new installed distro.
I will copy bitsperlong.h into asm-x86 as suggested.
Should other files be present in the above directory ?
Should I send a bug report to Mandriva ?
Thank you all for your help.
Bernard Pidoux
On Sun, Sep 27, 2009 at 01:16:41PM +0200, Bernard Pidoux wrote:
> The problem is that when I compile an application that never caused any
> problem before I get an error due to incorrect reference to
> <asm/bitsperlong>
>
> This was due to int-ll64.h including <asm/bitsperlong.h> which does not exists.
>
> Is the correct solution to replace symbolic link ?
>
> /usr/src/linux/include/asm->asm-x86
>
> by
>
> /usr/src/linux/include/asm->asm-generic
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 11:57 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 [this message]
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
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=4ABF5328.8020901@upmc.fr \
--to=bernard.pidoux@upmc.fr \
--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
Powered by JetHome