From: arnd@arndb.de
To: Bernard Pidoux <bernard.pidoux@upmc.fr>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: 2.6.31.1 BUG #include <asm/bitsperlong.h>
Date: Sun, 27 Sep 2009 16:58:18 +0000 [thread overview]
Message-ID: <200909271658.18646.arnd@arndb.de> (raw)
In-Reply-To: <4ABF4E36.4090703@upmc.fr>
On Sunday 27 September 2009 11:36:22 Bernard Pidoux wrote:
> 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’:
>
The problem is the '-I/usr/src/linux/include' part of the gcc command line.
See http://kernelnewbies.org/KernelHeaders for why this is wrong.
You should notify the maintainer of the package to fix this by removing
this option. The headers in /usr/include/ are sufficient to build user
code.
Arnd <><
next prev parent reply other threads:[~2009-09-27 16:58 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
2009-09-27 16:58 ` arnd [this message]
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=200909271658.18646.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=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