-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 27 March 2003 03:05 am, Jack Bowling wrote: > ** Reply to message from Michael Fratoni > on Wed, 26 Mar 2003 23:08:22 -0500
> > On Wednesday 26 March 2003 04:14 pm, Robert P. J. Day wrote: [...] > > > so, before i spend a lot of time on this, what is the function > > > of that symlink, and could having it point at a non-existent > > > kernel source directory be causing the rebuild of my NVIDIA > > > kernel src rpm to blow up with dozens of parse errors from > > > include files? [...] > > > (not having the kernel source directory for the current running > > > kernel doesn't affect anything else -- system runs fine otherwise.) > > > > But building kernel modules will fail, as modules require the headers > > from the kernel tree, not the headers installed in > > /usr/include/linux/, (which are the headers glibc was compiled with, > > and are provided by the glibc-kernheaders package). Any kernel module > > that tries to include system headers should generate warning messages > > similar to: > > #warning Using kernel header in userland! > > #warning Using kernel headers in userspace. > > > > In the case above, if /lib/modules/`uname -r`/build is a broken link, > > the build will fail with the above warnings followed by many parse > > errors. > > > > So, the short version is reinstall the kernel-source package if you > > want to build kernel modules. > > And most drivers will not be able to build until you do a "make > oldconfig" and "make dep" in the kernel source tree. I used to think so as well. And I'm sure I had to do both in the past at some point. However on the Pheobe list, this was disputed by Arjan van de Ven. (https://listman.redhat.com/pipermail/phoebe-list/2003-January/000762.html) I'll quote the relevent parts of the mail message: Begin quote: > make oldconfig > make dep > > ** THEN you can compile stuff against that kenel (like spca-50x driver > or wlan-ng drivers, vmware, etc etc.. but I have had better luck just > modifying the config file and using the built in wireless drivers :) > (peruse the psyche-list for examples) (To which Arjan replied:) I'm sorry to say it but you're full of shit here ;) All you just achieved is that you've blown away the proper kernel symbol version setup you need to compile against the kernel. 1) The *ONLY* place the kernel headers of the current kernel live is /lib/modules/`uname -r`/build/include not /usr/include/linux, not /usr/include/linux-2.4 not anything else this is per Linus' decree fwiw 2) You do NOT need all these steps; the headers RHL ships by default Just Work(tm) and will generate a module for the currently running kernel. End quote. Just an additional data point. ;) - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/ - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+g5AWn/07WoAb/SsRAqGjAJ4skz1/F6XomxEQcGm3CWwQyyb8ywCgi3IV biVxUZ8UcKeAOzt73JqdIfk= =CnXv -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
