Not if you recompile.
>
> > 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>.
>
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.
> 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.
> > 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.
>
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.
I see your point, but right now it's only academic and not practicable.
Marcus
-- /--------------------------------------------------------------------\ | Dr. Marcus O.C. Metzler | | |--------------------------------|-----------------------------------| | mocm@metzlerbros.de | http://www.metzlerbros.de/ | \--------------------------------------------------------------------/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/