Thanks for the tips. The nasa search found the same tulip.c source code, but that's a useful search technique to know about. I finally got the source for tulip.c to compile by adding a -I option to the gcc line--and that fixed the problem!
BUT-- Does anyone know what include files gcc uses by default? Using the "find" command, the only include tree for kernel headers is /usr/src/kernel-headers-2.2.12/include/linux. But these are NOT the headers I got when I left off the -I directive! Guess the "standard" headers must be pre-compiled somewhere, but shouldn't they have been pre-compiled with the current kernel headers? --Ray [EMAIL PROTECTED] On 06-Jan-00, you wrote: > i suggest checking on NASA's site (i forgot the url, go to > http://yahoo.aphroland.org and search for nasa) there may be an updated > driver, the author of most of the NIC drivers got into a arguement with > linus and alan(kernel maintainers) because the way he updates his drivers > are not what they like(or others), so chancesa re the drivers in the > kernel are (very?) old..even if the kernel is brand new. > > nate > > On Thu, 6 Jan 2000, Raymond L. Zarling wrote: > >> I got the source code for the 4/14/99 version of tulip from Greg's > page. It rayz >compiles fine, but I can't install it because it was > "compiled for kernel rayz >2.0.36" and I'm using 2.2.12. I can't figure > out where the 2.0.36 comes rayz >from; the only linux kernel headers I can > "find" (and therefore these must rayz >be the ones gcc uses? how is this > configured?) are in rayz >/usr/src/kernel-headers-2.2.12/include/linux > where UTS_RELEASE is correctly rayz >defined as 2.2.12. rayz > >> So... >> Can anyone give me a hint on how to compile tulip to run under > 2.2.12? rayz >Or any hints on what else to look for that could cause this > strange problem? rayz >
