Craig Sprout wrote:
> David Rankin wrote:
> >
> > Craig, thanks for the tulip.o and pci-scan.o, we almost had a winner!
> > Unfortunately, there is a Kernel mismatch. Yours were compiled with
> > 2.2.17 kernel, mine tells me it need 2.2.17mdk. Picky, picky, picky. I
> > am going to search for another tulip.c that hopefully I can get to
> > compile on my system. I still can't figure out why mine won't compile.
> > I'm going to research which gcc components I have installed and maybe
> > its just a library problem - who knows...
>
> Ooopppss...sorry about that. My other box is a 2.2.15mdk. Wonder if I
> compile it there if that will work...I suspect that your kernel is
> compiled with the "Set Version Information on symbols for All modules"
> option set to "No," which will force the module version to match the
> kernel version. You could rebuild your kernel with that option set to
> "Yes," and the modules should work flawlessly.
>
> If you like I can try it on my 2.2.15mdk kernel, and send you those
> binaries.
>
> Ain't this fun? :)
>
Yes it was, but I FINALLY GOT THAT SUCKER TO COMPILE !!! ; )
I got it to compile (both pci-scan.c and tulip.c) installed the modules and
it works like a champ! Don Becker of scyld.com had the answer I needed to
add -I/usr/src/linux-2.2.17/include to my gcc compile string. After doing so
it all worked! (I swear I had used -I/usr/src/linux/include) (linux is a
soft link to linux-2.2.17) Whatever the reason, Don's advice fixed the
problem.
Thanks to all
>
> --
> Craig Sprout
> Network Administrator
> Crown Parts and Machine, Inc.
> http://www.crownpartsandmachine.com/
--
David C. Rankin
Nacogdoches, Texas
