Re: compile probs, glibc, satlink.c (Planetc Feed)
On Fri, May 08, 1998 at 04:03:46PM +0200, Alexander Koch wrote: > I've a Planetc satfeed and there's a module satlink.c (.o > respectively) which doesn't want to compile w/ glibc. > No prob with that, I added a "-I/usr/i486-linuxlibc1/" to > the gcc call and it compiled. The recommended way of compiling libc5 binaries on hamm is to use "altgcc" and ensure that /usr/i486-linuxlibc1/bin is in the PATH before the regular bin directories. > I've installed the "libc5-altdev" beforehand and the libc5 and hopefully > this is enough. > > Now... I've a custom 2.0.33 kernel (not the Debian kernel- source > package). I've altered the links from /usr/include/asm/ and > /usr/include/linux/, of course. I'm compiling it and whenever I try to > insmod satlink.o it tells me it was compiled for 2.0.32 That's because libc5-altdev comes with its own set of kernel headers from 2.0.32. > and that doesn't match the actual kernel. I've that module version > information thing switched on in the kernel (which should help, since it > says it allows me to use modules compiled for another kernel version). > > Now... what did I do wrong? You didn't use the "-f" option to insmod: -f Attempt load the module even if the version of the running kernel and the version of the kernel for which the module was compiled do not match. HTH, Ray -- PATRIOTISM A great British writer once said that if he had to choose between betraying his country and betraying a friend he hoped he would have the decency to betray his country. - The Hipcrime Vocab by Chad C. Mulligan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
compile probs, glibc, satlink.c (Planetc Feed)
Hiya. I've a Planetc satfeed and there's a module satlink.c (.o respectively) which doesn't want to compile w/ glibc. No prob with that, I added a "-I/usr/i486-linuxlibc1/" to the gcc call and it compiled. I've installed the "libc5-altdev" beforehand and the libc5 and hopefully this is enough. Now... I've a custom 2.0.33 kernel (not the Debian kernel- source package). I've altered the links from /usr/include/asm/ and /usr/include/linux/, of course. I'm compiling it and whenever I try to insmod satlink.o it tells me it was compiled for 2.0.32 and that doesn't match the actual kernel. I've that module version information thing switched on in the kernel (which should help, since it says it allows me to use modules compiled for another kernel version). Now... what did I do wrong? Any help is appreciated... Thanks a lot, Alexander -- SGH Internet Division Alexander Koch, Administration Waldstr. 36, 30163 Hannover eMail: [EMAIL PROTECTED] Telefon: +49 511 391088, Fax +49 511 391307, http://www.sgh-net.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
