Problem with ISS-4 & EE16

Mitch Adair (mitch@acan.net)
Mon, 10 Mar 1997 23:18:08 -0600 (CST)


I just patched up 2.0.29 with ISS-4 with the following errors:

/usr/src/linux-2.0-ISS_4/include/linux/random.h needs config but has not included config file
random.c needs config but has not included config file
dgrs.c doesn't need config
filemap.c needs config but has not included config file
dir.c needs config but has not included config file
super.c needs config but has not included config file
symlink.c needs config but has not included config file
ip_masq_quake.c doesn't need config
eexpress.c: In function `eexp_xmit':
eexpress.c:450: `skb' undeclared (first use this function)
eexpress.c:450: (Each undeclared identifier is reported only once
eexpress.c:450: for each function it appears in.)
make[3]: *** [eexpress.o] Error 1
make[2]: *** [first_rule] Error 2
make[1]: *** [sub_dirs] Error 2
make: *** [linuxsubdirs] Error 2

The ones in eexpress.c cause the kernel compile to fail. Compiling eexpress.c
as a module will also fail, though the kernel will compile and run fine.
The sources were orig. 2.0.28, patched to 2.0.29 (with scripts/patch-kernel.)
I patched to ISS-4 with -p1, etc like in patch-kernel, there were no
.rej or problems and regular 2.0.29 compiles fine. I did make dep clean
zImage, and when it failed the first time I started over with 2.0.29 and
reapplyed the patch - in other words I don't *think* I screwed up the
patching...

The problem, I guess, is with this part of ISS-4:

diff -u --recursive --new-file vanilla/v2.0.29/linux/drivers/net/eexpress.c linux/drivers/net/eexpress.c
--- vanilla/v2.0.29/linux/drivers/net/eexpress.c Fri Jun 7 07:21:04 1996+++ linux/drivers/net/eexpress.c Sat Mar 8 21:15:44 1997
@@ -1,4 +1,4 @@
-/* $Id: eexpress.c,v 1.13 1996/05/19 15:59:51 phil Exp $
+/* $Id: eexpress.c,v 1.13.2.1 1997/03/09 02:14:21 davem Exp $
*
* Intel EtherExpress device driver for Linux
*
@@ -447,6 +447,7 @@
}
dev_tint(dev);
outb(SIRQ_en|irqrmap[dev->irq],ioaddr+SET_IRQ);
+ dev_kfree_skb(skb, FREE_WRITE);
return 0;
}

Everything is updated on the system to where it is supposed to be: gcc-2.7.2.1,
binutils-2.7.0.3, libc-5.4.17, etc. So, did I screw up applying the
patch or am I just the only person still lucky enough to have an EE16
to test this out on? :)

Mitch