[ale] make dep problems with 2.3.18 kernels?

Steven A. DuChene at VA Linux Systems sad at valinux.com
Thu Sep 30 15:37:29 EDT 1999


I am trying to get any 2.3.18 kernel (with or without various
ac patches from Alan Cox) to compile on my AMD 233 K6 system.
The system has 90+Mb of memory and has egcs-1.1.1 on it.
When I try to do a make dep I get the following sorts of errors
in various places:

make -C zftape fastdep
make[8]: Entering directory `/usr/src/linux-2.3.18/drivers/char/ftape/zftape'
/usr/src/linux-2.3.18/scripts/mkdep zftape-buffers.c zftape-buffers.h zftape-ctl.c zftape-ctl.h zftape-eof.c zftape-eof.h zftape-init.c zftape-init.h zftape-read.c zftape-read.h zftape-rw.c zftape-rw.h zftape-vtbl.c zftape-vtbl.h zftape-write.c zftape-write.h zftape_syms.c zftape_syms.h > .depend
make[8]: *** [fastdep] Error 135
make[8]: Leaving directory `/usr/src/linux-2.3.18/drivers/char/ftape/zftape'
make[7]: *** [_sfdep_zftape] Error 2
make[7]: Leaving directory `/usr/src/linux-2.3.18/drivers/char/ftape'
make[6]: *** [fastdep] Error 2
make[6]: Leaving directory `/usr/src/linux-2.3.18/drivers/char/ftape'
make[5]: *** [_sfdep_ftape] Error 2
make[5]: Leaving directory `/usr/src/linux-2.3.18/drivers/char'
make[4]: *** [fastdep] Error 2
make[4]: Leaving directory `/usr/src/linux-2.3.18/drivers/char'
make[3]: *** [_sfdep_char] Error 2
make[3]: Leaving directory `/usr/src/linux-2.3.18/drivers'
make[2]: *** [fastdep] Error 2
make[2]: Leaving directory `/usr/src/linux-2.3.18/drivers'
make[1]: *** [_sfdep_drivers] Error 2
make[1]: Leaving directory `/usr/src/linux-2.3.18'
make: *** [dep-files] Error 2

Is this a known problem? Has anyone seen this before? I was able to
get 2.3.18ac9 to compile fine on a 2U VA server with a Pentium III
processor and egcs-1.1.2 but I don't know if the egcs or the processor
could be the difference.

I have tried various suggestions like refetching the kernel tree or doing
a "make mrproper" but no change other than I get the "Error 135" problem
in different spots within the kernel tree when I changed source trees.
If I keep the same source tree (I first started with a 2.3.16 source tree
which I then applied the 17, 18 and ac9 patches to, but now I am working
with a straight 2.3.18 tree with the ac10 patch) it seems to always occur
in the same spot. The earlier patched up source tree did this in the
linux/net/sched directory and as you can see from the above I am now getting
it in the linux/drivers/char/ftape/zftape directory.
-- 
Steven A. DuChene	sad at valinux.com
Southeast US Systems Engineer
VA Linux Systems	http://www.valinux.com






More information about the Ale mailing list