From: Keith Owens <kaos@ocs.com.au>
To: Miles Lane <miles@megapathdsl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5-ac15 -- Unresolved symbols "gameport_register_port" and "gameport_unregister_port" in char/joystick/[cs461x.o, emu10k1-gp.o, lightning.o, ns558.o, pcigame.o]
Date: Tue, 19 Jun 2001 19:31:55 +1000 [thread overview]
Message-ID: <18479.992943115@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "18 Jun 2001 12:31:28 MST." <992892690.11752.0.camel@agate>
On 18 Jun 2001 12:31:28 -0700,
Miles Lane <miles@megapathdsl.net> wrote:
>I don't know if this is due to symbols not being exported or due
>to some failed dependency structuring in "make menuconfig".
>depmod: *** Unresolved symbols in
>/lib/modules/2.4.5-ac15/kernel/drivers/char/joystick/cs461x.o
>depmod: gameport_register_port
>depmod: gameport_unregister_port
Works for me with your .config fragment. It could be a menu order
dependency, save .config, make oldconfig, compare the saved and new
.config. If they are different then it was a menuconfig order
problem[*], if they are the same then I need your full .config, not
just an extract.
[*] A good reason to use CML2 ;)
next prev parent reply other threads:[~2001-06-19 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 19:31 2.4.5-ac15 -- Unresolved symbols "gameport_register_port" and "gameport_unregister_port" in char/joystick/[cs461x.o, emu10k1-gp.o, lightning.o, ns558.o, pcigame.o] Miles Lane
2001-06-19 9:31 ` Keith Owens [this message]
2001-06-19 9:41 ` 2.4.5-ac15 -- Unresolved symbols "gameport_register_port" and "gameport_unregister_port" in char/joystick/[cs461x.o, emu10k1 Alan Cox
2001-06-19 12:44 ` 2.4.5-ac15 -- Unresolved symbols "gameport_register_port" and "gameport_unregister_port" in char/joystick/[cs461x.o, emu10k1-gp.o, lightning.o, ns558.o, pcigame.o] axel
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=18479.992943115@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
/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