From: Christoph Hellwig <hch@infradead.org>
To: mocm@mocm.de
Cc: Michael Hunold <hunold@convergence.de>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: DVB Include files
Date: Wed, 25 Jun 2003 19:15:32 +0100 [thread overview]
Message-ID: <20030625191532.A1083@infradead.org> (raw)
In-Reply-To: <16121.58735.59911.813354@sheridan.metzler>; from mocm@metzlerbros.de on Wed, Jun 25, 2003 at 08:09:51PM +0200
On Wed, Jun 25, 2003 at 08:09:51PM +0200, Marcus Metzler wrote:
> > If the structures change incompatibly you're fucked anyway. Better
>
> Not necessarily, e.g. changing
>
> #define AUDIO_SET_ATTRIBUTES _IOW('o', 17, audio_attributes_t)
> #define AUDIO_SET_KARAOKE _IOW('o', 18, audio_karaoke_t)
>
> to
>
> #define AUDIO_SET_ATTRIBUTES _IOW('o', 47, audio_attributes_t)
> #define AUDIO_SET_KARAOKE _IOW('o', 48, audio_karaoke_t)
>
> or
In that case yes, you are screwed. Your ABI just changed incompatibly.
> Anyway, even in user/include it should be under linux/dvb because
> that's just what it is Linux DVB. So the app has to include
> <linux/dvb/xxx.h>.
No! <linux/*.h> is the namesapce for kernelheaders. Currently they're
still in the the user includes, too (due to legacy reasons). The
DVD API must move to a directory outside <linux/dvb>.
If you userland packages add headers to /usr/include/linux/ they
are totally bogus.
> I don't care what distributions do. When I get a new kernel (no
> packages), I use the includes from that kernel and compile my apps
> with that.
And that's wrong. You must always compile against the kernel headers
that your libc was compiled against.
next prev parent reply other threads:[~2003-06-25 18:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 15:06 DVB Include files Sam Ravnborg
2003-06-25 15:08 ` Christoph Hellwig
2003-06-25 15:42 ` Sam Ravnborg
2003-06-25 16:17 ` Michael Hunold
2003-06-25 16:49 ` Marcus Metzler
2003-06-25 16:55 ` Christoph Hellwig
2003-06-25 17:13 ` Marcus Metzler
2003-06-25 17:16 ` Christoph Hellwig
2003-06-25 17:22 ` Marcus Metzler
2003-06-25 17:24 ` Christoph Hellwig
2003-06-25 17:30 ` Marcus Metzler
2003-06-25 17:50 ` Christoph Hellwig
2003-06-25 18:09 ` Marcus Metzler
2003-06-25 18:15 ` Christoph Hellwig [this message]
2003-06-25 18:43 ` Marcus Metzler
2003-06-25 19:42 ` Jörn Engel
2003-06-25 20:09 ` Marcus Metzler
2003-06-25 20:23 ` Jörn Engel
2003-06-25 20:48 ` Marcus Metzler
2003-06-25 21:03 ` Christoph Hellwig
2003-06-25 21:38 ` Marcus Metzler
2003-06-26 13:54 ` Henning P. Schmiedehausen
2003-06-25 23:08 ` Alan Cox
2003-06-26 8:18 ` Michael Hunold
2003-06-26 8:24 ` Christoph Hellwig
2003-06-26 13:20 ` Johannes Stezenbach
2003-06-25 21:03 ` Christoph Hellwig
2003-06-25 17:27 ` Jörn Engel
2003-06-25 17:49 ` Christoph Hellwig
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=20030625191532.A1083@infradead.org \
--to=hch@infradead.org \
--cc=hunold@convergence.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mocm@mocm.de \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).