public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: mocm@mocm.de
Cc: Christoph Hellwig <hch@infradead.org>,
	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 22:03:55 +0100	[thread overview]
Message-ID: <20030625220355.A13814@infradead.org> (raw)
In-Reply-To: <16121.60747.537424.961385@sheridan.metzler>; from mocm@metzlerbros.de on Wed, Jun 25, 2003 at 08:43:23PM +0200

On Wed, Jun 25, 2003 at 08:43:23PM +0200, Marcus Metzler wrote:
>  > In that case yes, you are screwed.  Your ABI just changed incompatibly.
> 
> Not if you recompile.

If you need to recompile your ABI changed.  And yes, then your absolutely
screwed.

>  > 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>.
>  > 
> 
> Why (It's DVB by the way)? It's as close to the kernel as ls or cat
> and having two sets of the same includes is stupid. 

No, it's not.  One if for the driver you compile and one for the application.

>  > If you userland packages add headers to /usr/include/linux/ they
>  > are totally bogus.
>  > 
> 

> What packages? You are always talking about packages. There are no packages.
> There are only the kernel and my app. Nothing else. No copying of headers.

Then you need to add a package with the userland header (which, as I already
said might be exactly the same ones as those in the kernel tree).

>  > And that's wrong.  You must always compile against the kernel headers
>  > that your libc was compiled against.
>  > 
> 
> There is no one who does that, not even distributions. The includes
> needed for libc are far less prone to change than v4l or dvb. And not
> as linux specific.

Oh yes, everyone does.  Ever looked at an errata kernel from RH, SuSE
or Debian?  Yes, they never change what's /usr/include/.

> I see your point, but right now it's only academic and not practicable.

It's how Linux works.  If you don't like that play with SCO Unix or MacOS.


  parent reply	other threads:[~2003-06-25 20:49 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
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 [this message]
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=20030625220355.A13814@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