Re: 2.5 kbuild: use of '-z muldefs' for LD?

[Christoph Hellwig <hch@infradead.org>]

On Mon, Jun 09, 2003 at 01:56:59PM +0200, Jaroslav Kysela wrote:
> one object file for more targets. Example:
> 
> ------
> snd-ice1712-objs := ice1712.o delta.o hoontech.o ews.o ak4xxx.o
> snd-ice1724-objs := ice1724.o amp.o revo.o aureon.o ak4xxx.o
> 
> # Toplevel Module Dependency
> obj-$(CONFIG_SND_ICE1712) += snd-ice1712.o
> obj-$(CONFIG_SND_ICE1724) += snd-ice1724.o
> ------
> 
> The ak4xxx.o module is shared and has defined a few public functions.
> Unfortunately, the default build-in.o rule fails when targets are 
> requested to be included into the solid kernel because the public 
> functions are duplicated in snd-ice1712.o and snd-ice17124.o.
> 
> I can instruct the ld compiler to ignore the multiple definitions using 
> '-z muldefs':
> 
> EXTRA_LDFLAGS = -z muldefs
> 
> But it seems like a hack for me.
> Does anybody have another idea to solve my problem?

Move ak4xxx.o out of the multi-obj rules.  Just declare a new helper-
config option CONFIG_SND_AK4XXX that gets defined by all drivers
using it and add

obj-$(CONFIG_SND_AK4XXX)	+= ak4xxx.o

You'll just have to make sure to export all symbols in 2.5