Re: Unresolved symbols in "make install" of netdrivers.tgz

Steinar Bang <[email protected]>
Newsgroups gmane.linux.drivers.tulip.general
Organization Probably a good idea
Message-ID <[email protected]>
>>>>> Donald Becker <[email protected]>:

> When you compile, does the -I... include path point to the proper
> kernel header files for the kernel that you attempt to install with?

Good call!  Each kernel-image package in debian, has a matching
kernel-headers package.

That got me almost through the install.  Right now make install only
gets a single unresolved symbol message:
	depmod: *** Unresolved symbols in /lib/modules/2.4.19-686/kernel/drivers/pcmcia/cb_shim.o

I installed the kernel-image-2.4.19-686 package[1] and the matching
kernel-image-2.4.19-686 package[2] (these are the newest 2.4 kernel
packages from debian.  I picked the 2.4.19-2 release from debian
unstable).  The make commands were:
	make -k KERN_INCLUDE=/usr/src/kernel-headers-2.4.19-686/include 
	make -k KERN_INCLUDE=/usr/src/kernel-headers-2.4.19-686/include install

So far I have tried the following approaches to avoid the missing
symbols error message:
 1. Tried not building PCMCIA/cardbus support by using the make
    command:
	make -k KERN_INCLUDE=/usr/src/kernel-headers-2.4.19-686/include PCMCIA=/tmp

 2. Tried to move away the driver_ops.h fil the Makefile looks for,
    ie. 
	cd /usr/src/kernel-headers-2.4.19-686/include/
	mv pcmcia pcmcia.disabled

 3. Tried commenting out the stuff that adds cb_shim.o, ie.
	ifeq ($(wildcard $(PCMCIA)/pcmcia/driver_ops.h),"")
	   $(warning The PCMCIA header files could not be found.$(newline)\
	 No CardBus support will be built.)
	else
	#  OFILES += cb_shim.o
	#  CARDBUS= 3c575_cb.o epic_cb.o tulip_cb.o realtek_cb.o
	#  CARDBUS-FLAGS = -DCARDBUS -I$(KERN_INCLUDE) -I$(PCMCIA) -I/usr/include
	#  CB_SHIM = cb_shim.o
	endif

 4. Tried installing the kernel-pcmcia-modules-2.4.19-686 package[3].

For the last attempt I deinstalled the kernel package, and completely
removed the modules directory for this kernel.

Perhaps attempt 1, 2 or 3 would have worked better if I had
reinstalled the kernel between the attempts?  (The reason I didn't, is
that I have to reboot into 2.2.19, every time I need network access,
and this takes some time)


- Steinar

[1] <http://packages.debian.org/unstable/base/kernel-image-2.4.19-686.html>
[2] <http://packages.debian.org/unstable/devel/kernel-headers-2.4.19-686.html>
[3] <http://packages.debian.org/unstable/base/kernel-pcmcia-modules-2.4.19-686.html>


_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.