/lib/modules/`uname -r`/build should be a link to kernel source code.
Have you kernel-source.rpm installed ? .
ls -l /lib/modules/`uname -r`/build
lrwxrwxrwx 1 root root 27 Sep 1 01:08 /lib/modules/2.4.27/build -> /usr/s=
On Wed, 2004-09-15 at 19:59, Trevor Smith wrote:
> On September 15, 2004 12:03 pm, John Haxby wrote:
> > Seriously, it looks as though something has got messed up. =20
> > /lib/modules/`uname -r`/build is supposed to be a symbolic link to the
> > sources. Do you have other /lib/modules/* directories to compare
> > against? Is "build" a symbolic link or a directory?
> I have another kernel directory and it also contains a "build" directory =
> is *NOT* a symlink. This is FC2, kernels 2.6.5-1.358 and 2.6.8-1.521. Shr=
> The good news is, ndiswrapper *does* compile properly *without* the kerne=
> source, at least on my machine. Or, rather, it compiled without error, bu=
> was told I needed a certain file which was not present so I panicked and=20
> installed the kernel sources and ndiswrapper *still* compiled without err=
> but the file in question (wlan_radio_averatec_5110hx) was *still* not pre=
> so I said screw it and proceeded and all was well. So, technically, I do =
> have kernel sources present, but the compile of ndis showed no difference=
> before or after installing the sources and I don't have a symlink in the=20
> location specified above so presumably the make process for ndiswrapper w=
> not have found my kernel sources anyway.
> Long story short, ndiswrapper seems to work beautifully and pretty much "=
> of the box", as long as I didn't worry too much about getting messages=20
> exactly as expected in this article (which is the best I found for walkin=
> through the install):
S=E9rgio M. B.