From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Bug in DVB header files
Date: Mon, 02 Mar 2009 18:07:03 +0100 [thread overview]
Message-ID: <49AC1237.9000104@cadsoft.de> (raw)
Reinhard Nissl made me aware of the fact that with recent versions
of the driver from http://linuxtv.org/hg/v4l-dvb there is apparently
someting wrong with the header files. Doing
#include <linux/videodev2.h>
#include <linux/dvb/audio.h>
results in
.../linux/dvb/audio.h:79: error: 'uint16_t' does not name a type
Doing the #includes in reverse order gives
/usr/include/sys/select.h:78: error: conflicting declaration 'typedef struct fd_set fd_set'
/usr/include/linux/types.h:12: error: 'fd_set' has a previous declaration as 'typedef struct __kernel_fd_set fd_set'
The only way to compile VDR with the recent driver is to revert to
the header files as they were before the change labeled
"backport include changes on some .h files"
Klaus
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
reply other threads:[~2009-03-02 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49AC1237.9000104@cadsoft.de \
--to=klaus.schmidinger@cadsoft.de \
--cc=linux-dvb@linuxtv.org \
--cc=linux-media@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