From: Miles Lane <miles@megapath.net>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org,
Ruurd Reitsma <R.A.Reitsma@wbmt.tudelft.nl>,
Norberto Pellicci <pellicci@home.com>
Subject: Re: 2.4.1 -- Unresolved symbols in radio-miropcm20.o
Date: Tue, 30 Jan 2001 23:12:39 -0800 [thread overview]
Message-ID: <3A77BAE7.3CC016AE@megapath.net> (raw)
In-Reply-To: <4987.980895146@ocs3.ocs-net>
Thanks Keith,
I don't get any errors if I add these lines to my .config
file:
CONFIG_SOUND_OSS=m
CONFIG_SOUND_ACI_MIXER=m
Ruurd, are you maintaining this driver?
If not, is anyone else willing to hack the config scripts
to enforce this dependency? This is not my area of
competency.
Thanks,
Miles
Keith Owens wrote:
>
> On Tue, 30 Jan 2001 13:08:12 -0800,
> Miles Lane <miles@megapath.net> wrote:
> >depmod: *** Unresolved symbols in
> >/lib/modules/2.4.1/kernel/drivers/media/radio/radio-miropcm20.o
> >depmod: aci_write_cmd
> >depmod: aci_indexed_cmd
> >depmod: aci_write_cmd_d
>
> Those symbols are defined in drivers/sound/aci.c but are not exported
> for other modules to use. The aci and miropcm20 code needs to be
> changed to support use as modules. Also the config.in files need
> fixing for these files, it is possible to select combinations of aci
> and miropcm20 that will fail to link (miropcm20 built in, aci not
> selected or selected as a module) or fail to load (miropcm20 selected
> as a module, aci not selected).
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 7:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 21:08 2.4.1 -- Unresolved symbols in radio-miropcm20.o Miles Lane
2001-01-30 22:52 ` Keith Owens
2001-01-31 7:12 ` Miles Lane [this message]
2001-01-31 8:46 ` Arjan van de Ven
2001-01-31 8:48 ` Keith Owens
2001-01-31 10:55 ` Peter Samuelson
2001-01-31 11:07 ` Arjan van de Ven
[not found] ` <14967.62433.949844.559264@wire.cadcamlab.org>
2001-01-31 11:19 ` Arjan van de Ven
2001-01-31 11:48 ` Peter Samuelson
2001-01-31 16:22 ` Ruurd A. Reitsma
2001-01-31 20:21 ` Robert Siemer
2001-02-01 15:50 ` Robert Siemer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A77BAE7.3CC016AE@megapath.net \
--to=miles@megapath.net \
--cc=R.A.Reitsma@wbmt.tudelft.nl \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pellicci@home.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox