public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Cheney <ccheney@cheney.cx>
To: linux-kernel@vger.kernel.org
Subject: 2.5.47+ input as module broken
Date: Sat, 16 Nov 2002 23:24:34 -0600	[thread overview]
Message-ID: <20021117052434.GF26199@cheney.cx> (raw)

When CONFIG_INPUT=m is set the following occurs:

        ld -m elf_i386 -e stext -T arch/i386/vmlinux.lds.s arch/i386/kernel/head.o arch/i386/kernel/init_task.o  init/built-in.o --start-group  usr/built-in.o  arch/i386/kernel/built-in.o  arch/i386/mm/built-in.o  arch/i386/mach-generic/built-in.o  kernel/built-in.o  mm/built-in.o  fs/built-in.o  ipc/built-in.o  security/built-in.o  crypto/built-in.o  lib/lib.a  arch/i386/lib/lib.a  drivers/built-in.o  sound/built-in.o  arch/i386/pci/built-in.o  net/built-in.o --end-group  -o vmlinux
drivers/built-in.o(.text+0x39b43): In function `kd_nosound':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x39b5c): In function `kd_nosound':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x39c07): In function `kd_mksound':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x3a8a2): In function `kbd_bh':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x3a8b0): In function `kbd_bh':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x3a8c1): more undefined references to `input_event' follow
drivers/built-in.o(.text+0x3ad73): In function `kbd_connect':
: undefined reference to `input_open_device'
drivers/built-in.o(.text+0x3ad97): In function `kbd_disconnect':
: undefined reference to `input_close_device'
drivers/built-in.o(.init.text+0x2391): In function `kbd_init':
: undefined reference to `input_register_handler'

Chris Cheney

cc: any replies

             reply	other threads:[~2002-11-17  5:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17  5:24 Chris Cheney [this message]
2002-11-18 18:35 ` 2.5.47+ input as module broken James Simmons

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=20021117052434.GF26199@cheney.cx \
    --to=ccheney@cheney.cx \
    --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