Hello all,
I am trying to figure the best solution for our problem. We reuse
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?
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:20 EST