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:36:22 +0200 [thread overview]
Message-ID: <4ABF4E36.4090703@upmc.fr> (raw)
This is a user space application.
Here is Gcc error message :
gcc -Wall -Wstrict-prototypes -O2 -ggdb2 -funsigned-char -D__LINUX__ -Wformat-security -D_FORTIFY_SOURCE=2 -DPROTOTYPES -I../lib -I/usr/src/linux/include -fstack-check -fstack-protector-all -c listen.c
Dans le fichier inclus à partir de /usr/include/asm/types.h:4,
à partir de /usr/src/linux/include/linux/types.h:4,
à partir de /usr/src/linux/include/linux/if_ether.h:24,
à partir de /usr/include/net/ethernet.h:27,
à partir de listen.c:21:
/usr/src/linux/include/asm-generic/int-ll64.h:11:29: erreur: asm/bitsperlong.h : Aucun fichier ou dossier de ce type
listen.c: In function ‘main’:
On Sun, 27 Sep 2009 13:16:41 +0200
Bernard Pidoux <bernard.pidoux@upmc.fr> 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>
is this a userspace application? or some kernel module?
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next reply other threads:[~2009-09-27 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 11:36 Bernard Pidoux [this message]
2009-09-27 11:57 ` 2.6.31.1 BUG #include <asm/bitsperlong.h> 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
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=4ABF4E36.4090703@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.