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
> > 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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 30 2003 - 22:00:21 EST