-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 24 August 2003 14:43, Oleg Goldshmidt wrote: > Alex Veber <[EMAIL PROTECTED]> writes: > > Thats not always true, for example in Gentoo if you choose to > > compile a NPTL enabled glibc /usr/src/linux MUST point to a recent > > 2.6 kernel tree, also the nvidia binary driver compiles against > > headers from /usr/src/linux, basically this done so you can switch > > kernels and recompile binary (or not binary like ALSA) drivers with > > ease. > > I don't have any experience with Gentoo, and from your email address I > assume you do. So maybe you can explain a couple of things to me. > > I don't follow the point about binary drivers compiled against headers > in /usr/src/linux. I must admit I have avoided binary-only drivers for > now, but what do they care if I have the right directory if they are > binary already? As long as I am using exactly the same kernel as the > one the driver was compiled against it won't care if I have the kernel > sources at all, let alone in a particular place in my tree. > > Are you sure that glibc compilation cannot be pointed to the right > kernel tree via a flag to configure or something? I would be very much > surprised. I assume glibc is glibc even on Gentoo, and there is a > --with-headers configure option to specify an alternate location for > kernel headers. The default, by the way, is not under > /usr/src/linux/include, but under /usr/include, as appropriate.
The headers glibc compiled against are not dependant on the current kernel installed. In Gentoo, there's a seperate package called linux-headers which installs under /usr/include/linux, and glibc is built against it (emerge -pe glibc will show linux-headers as a dependency) using --with-headers (this is somewhat simplification of the real situtation, as it'll try to build against 2.5/2.6 headers if exists, the ebuild will shed more light on the issue). It is the same as LinuxFromScratch's apparoach. For more info about it see: http://lfs.learnbyexample.com/view/4.1/chapter06/kernel.html Specially the paragraph titled "Why we copy the kernel headers and don't symlink them". > In any case, if a piece of a third-party software is looking for a > hardwired path generally speaking that's a bug. The path should be > configurable via environment, configuration options, or in some other > way. If you cannot fix it then you'd better create the link while > reporting the bug at the same time. Can't remember about nvidia (haven't used it for sometime now) but other binary drivers, like vmware, don't use /usr/src/linux but /lib/modules/`uname -r`/build/include - -- Meir Kriheli MKsoft systems http://www.mksoft.co.il -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/SQBVRkS5DWK1mZkRAs/kAKCcSJ/OCyLnP55pU2haP5FHfvu/RwCfbllw 8dlw90JXSzjxoN3m8zfi9sg= =fRn1 -----END PGP SIGNATURE----- ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
