From: Valdis.Kletnieks@vt.edu
To: Duncan Sands <baldrick@wanadoo.fr>
Cc: koraq@xs4all.nl, linux-kernel@vger.kernel.org
Subject: Re: [2.4.22-pre7] speedtouch.o unresolved symbols
Date: Fri, 25 Jul 2003 11:12:13 -0400 [thread overview]
Message-ID: <200307251512.h6PFCD9g004415@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 25 Jul 2003 16:43:31 +0200." <200307251643.32003.baldrick@wanadoo.fr>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
On Fri, 25 Jul 2003 16:43:31 +0200, Duncan Sands said:
> From drivers/usb/Config.in
>
> if [ "$CONFIG_ATM" = "y" -o "$CONFIG_ATM" = "m" ]; then
> dep_tristate ' Alcatel Speedtouch USB support' CONFIG_USB_SPEEDTOUCH $CONFIG_ATM $CONFIG_USB
> fi
>
> Now the question is: why is this not enough?
Hmm.. I don't have a 22-pre7 tree handy, what's the relevant reference in
drivers/usb/Makefile look like? I'm guessing a missing 'ifeq' or
obj-$(CONFIG_mumble) in there, so speedtch.o gets build even if the
required flags aren't set?
Other possibility is a missing EXPORT_SYMBOL() that's horquing things up
if you have CONFIG_ATM=m rather than y? (Yes, I know it's a 'bool' in net/Config.in,
doesn't mean you can't get an 'm' in there anyhow. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-07-25 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 20:20 [2.4.22-pre7] speedtouch.o unresolved symbols koraq
2003-07-24 21:35 ` koraq
2003-07-25 6:55 ` Duncan Sands
2003-07-25 14:26 ` Valdis.Kletnieks
2003-07-25 14:43 ` Duncan Sands
2003-07-25 15:12 ` Valdis.Kletnieks [this message]
2003-07-26 4:20 ` koraq
2003-07-26 11:05 ` Duncan Sands
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=200307251512.h6PFCD9g004415@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=baldrick@wanadoo.fr \
--cc=koraq@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).