From: Michal Januszewski <spock@gentoo.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: [PATCH] Fix fb.h breaking compilation of userspace programs
Date: Sat, 4 Sep 2004 18:35:16 +0200 [thread overview]
Message-ID: <20040904163516.GA23640@spock.one.pl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 573 bytes --]
Hi,
The latest changes introduced to the fb structs in linux/fb.h make
compilation of userspace programs break with:
include/linux/fb.h:305: error: field `modelist' has incomplete type
This is caused by struct list_head not being seen from userspace. The
attached patch is a possible fix for this problem.
Live long and prosper.
--
Michal 'Spock' Januszewski Gentoo Linux Developer
cell: +48504917690 http://dev.gentoo.org/~spock/
JID: spock@im.gentoo.org freenode: #gentoo-dev, #gentoo-pl
[-- Attachment #1.2: fb-list.patch --]
[-- Type: text/plain, Size: 877 bytes --]
diff -Naur linux-2.6.9-rc1/include/linux/list.h linux-2.6.9-rc1-a/include/linux/list.h
--- linux-2.6.9-rc1/include/linux/list.h 2004-09-04 18:18:18.000000000 +0200
+++ linux-2.6.9-rc1-a/include/linux/list.h 2004-09-04 18:23:55.401859688 +0200
@@ -1,6 +1,10 @@
#ifndef _LINUX_LIST_H
#define _LINUX_LIST_H
+struct list_head {
+ struct list_head *next, *prev;
+};
+
#ifdef __KERNEL__
#include <linux/stddef.h>
@@ -25,10 +29,6 @@
* using the generic single-entry routines.
*/
-struct list_head {
- struct list_head *next, *prev;
-};
-
#define LIST_HEAD_INIT(name) { &(name), &(name) }
#define LIST_HEAD(name) \
@@ -696,7 +696,5 @@
({ tpos = hlist_entry(pos, typeof(*tpos), member); 1;}); \
pos = rcu_dereference(pos->next))
-#else
-#warning "don't include kernel headers in userspace"
#endif /* __KERNEL__ */
#endif
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-09-04 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 16:35 Michal Januszewski [this message]
2004-09-04 21:42 ` [PATCH] Fix fb.h breaking compilation of userspace programs Antonino A. Daplas
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=20040904163516.GA23640@spock.one.pl \
--to=spock@gentoo.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).