public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Griesser <tuxx@aon.at>
To: Sven Vermeulen <sven.vermeulen@rug.ac.be>
Cc: Linux-kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.7 build failure : esssolo1.c troubles
Date: Sat, 21 Jul 2001 14:47:24 +0200	[thread overview]
Message-ID: <20010721144724.A27527@aon.at> (raw)
In-Reply-To: <20010721142539.A6276@Zenith.starcenter>
In-Reply-To: <20010721142539.A6276@Zenith.starcenter>

On Sat, Jul 21, 2001 at 02:25:39PM +0200, you wrote:
> drivers/sound/sounddrivers.o: In function `solo1_probe':
> drivers/sound/sounddrivers.o(.text.init+0x3ab): undefined reference to \
>   `gameport_register_port'
> drivers/sound/sounddrivers.o: In function `solo1_remove':
> drivers/sound/sounddrivers.o(.text.init+0x4d7): undefined reference to \
>   `gameport_unregister_port'
> make: *** [vmlinux] Error 1

AFAIK, gameport_register_port and gameport_unregister_port are defined
in <linux/gameport.h>, which is included at the beginning of esssolo1.c
with the following code:

#if defined(CONFIG_INPUT_ANALOG) || defined(CONFIG_INPUT_ANALOG_MODULE)¶
#include <linux/gameport.h>¶
#else¶

Maybe one of those Values (CONFIG_INPUT_ANALOG{_MODULE, }) is not
defined?

regards, alexx
-- 
|   .-.   | Alexander Griesser <tuxx@aon.at> -=- ICQ:63180135 |  .''`. |
|   /v\   |  http://www.tuxx-home.at -=- Linux Version 2.4.6  | : :' : |
| /(   )\ |  FAQ zu at.linux:  http://alfie.ist.org/LinuxFAQ  | `. `'  |
|  ^^ ^^  `---------------------------------------------------´   `-   |

  reply	other threads:[~2001-07-21 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-21 12:25 2.4.7 build failure : esssolo1.c troubles Sven Vermeulen
2001-07-21 12:47 ` Alexander Griesser [this message]
2001-07-21 14:56   ` Sven Vermeulen
  -- strict thread matches above, loose matches on Subject: below --
2001-07-21 15:07 Frank Davis
2001-07-21 15:12 ` 2.4.7 " Keith Owens

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=20010721144724.A27527@aon.at \
    --to=tuxx@aon.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sven.vermeulen@rug.ac.be \
    /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