On Fri, May 03, 2002 at 04:05:52PM -0500, Mark H. Wood wrote:
> There is a reason that this issue keesp rising from the grave. I just
> downloaded the glibc 2.2.5 source tarball and in INSTALL I find
> [begin quote]
> Specific advice for Linux systems
> If you are installing GNU libc on a Linux system, you need to have
> the header files from a 2.2 kernel around for reference. You do not
> need to use the 2.2 kernel, just have its headers where glibc can access
> at them. The easiest way to do this is to unpack it in a directory
> such as `/usr/src/linux-2.2.1'. In that directory, run `make config'
> and accept all the defaults. Then run `make include/linux/version.h'.
> Finally, configure glibc with the option
> `--with-headers=/usr/src/linux-2.2.1/include'. Use the most recent
> kernel you can get your hands on.
> An alternate tactic is to unpack the 2.2 kernel and run `make
> config' as above. Then rename or delete `/usr/include', create a new
> `/usr/include', and make the usual symbolic links of
> `/usr/include/linux' and `/usr/include/asm' into the 2.2 kernel
> sources. You can then configure glibc with no special options. This
> tactic is recommended if you are upgrading from libc5, since you need
> to get rid of the old header files anyway.
> Note that `/usr/include/net' and `/usr/include/scsi' should *not* be
> symlinks into the kernel sources. GNU libc provides its own versions
> of these files.
> [end quote]
I believe this is only for building Glibc, but all apps that depend on Glibc
should use whatever kernel headers that glibc is using...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
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 : Tue May 07 2002 - 22:00:25 EST