Anne Wilson wrote:
On Tuesday 07 November 2006 23:04, Ric Moore wrote:
On Tue, 2006-11-07 at 22:21 +0000, Anne Wilson wrote:
On Tuesday 07 November 2006 20:24, Warren Sturm wrote:
That will probably be kernel-devel package. However, on mine it points
to /usr/src/kernels/2.6.18-1.2798.fc6-xen-i686
but i have
/usr/src/kernels/2.6.18-1.2798.fc6-i686/ from the devel package. So
there is some fun waiting when I try to compile new kernel modules.
ls -al /lib/modules/2.6.18-1.2798.fc6/build
lrwxrwxrwx 1 root root 47 Nov 1
12:15 /lib/modules/2.6.18-1.2798.fc6/build ->
../../../usr/src/kernels/2.6.18-1.2798.fc6-i586
And this still lists in a flashing red. I must be missing something
obvious. The 'build' file is definitely there.
I usually delete that link... no need for all the ../../../ stuff.
then I relink:
ln -s /usr/src/kernels/2.6.18-1.2798.fc6-i586 build
which will fix the link/filename 'source' which points to 'build'.
You are using i586 and not i686? Plenty of strangeness going around. I'm
gonna reboot to see if my glibc was the culprit of some of my problems.
OK - done that, but still
make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686'
CC [M] /home/anne/Downloads/gspcav1-20060925/gspca_core.o
/home/anne/Downloads/gspcav1-20060925/gspca_core.c:36:26: error:
linux/config.h: No such file or directory
I've built things in the past and never got this stuck. Am I still missing
some package/conf or is it just a brain-fart?
Kernel change? Haven't built against 2.6.18, so I can't say. Did you
look at the include line and check that the file is there? Has it moved?
Is it no longer the "right way" to get config? Did you need to make
clean, or even menuconfig or xconfig?
--
Bill Davidsen <davidsen@xxxxxxx>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
