Shouldn't glibc-devel r: kernel-headers?

[Tomasz Kłoczko]

On Wed, 16 Oct 2002, wrobell wrote:

> On Tue, Oct 15, 2002 at 10:10:58PM +0200, Michal Moskal wrote:
> > On Tue, Oct 15, 2002 at 08:58:54PM +0200, Jakub Bogusz wrote:
> > > On Sat, Oct 12, 2002 at 09:21:54PM +0200, Andrzej Krzysztofowicz wrote:
> > > > > There are some situations when you should recompile
> > > > > your glibc, but they are rare.
> > > > 
> > > > Kernel 2.4+ headers are no longer intended to be used in userspace.
> > > > Eg., you must hack them in some places to use them with C++.
> > > 
> > > Where? I didn't change anything in 2.4 headers and don't see such
> > > problems (after recompiling glibc on those headers).
> > > But I did see strange type conflicts when I tried to use fresh kernel
> > > headers with glibc compiled on older headers (that was in 2.2.1x era).
> > > Those problems dissapeared after recompiling glibc.
> > > 
> > > > So providing own copy of hacked kernel-headers included into glibc-devel
> > > > seems to be the only choice when we switch into 2.4/2.6.
> > > 
> > > I agree - kernel headers in /usr/include/{asm,linux}, in glibc-devel
> >                                                 ^^^^^
> > 
> > If program does include <linux/...> it probably should
> > -I/usr/src/linux.
> -I/usr/src/linux/include :-)
> 
> But... which files will be included first when you specify
> -I/usr/src/linux/include?  These in /usr/include or these in -I/usr/src...?

IIRC if some package will require kernel headers during compile with
-D__KERNEL__ it will be kernel module. All not __KERNEL__ depedent code in
this headers probaly in near or slightly far fure will moved to *libc
headers.
Now searation between kernel and libc headres isn't complet so we still
must use headers from kernel and libc (glibc or other libc like uClibc or
dietlibc).

kloczek
-- 
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek at rudy.mif.pg.gda.pl*