Re: 2.5.40 compile errors with my CONFIG options (included)

["Bill Beebe" <wbeebe@cfl.rr.com>]

I had this same problem with 2.5.4x in general, and got this very helpful clue
from Rusty Lynch:

The problem is that when Virtual Terminal support is built into the kernel
(not a module) then Input support also needs to be built into the kernel
because it is making function calls that are implemented in the VT section.

To fix this, change the build input support to be built in the kernel instead
of building it as a module.  This can be done from "make xconfig" by
clicking on the "Input device support" on the left, and then change the "Input
devices (needed for keyboard, mouse, ...)" so that it has
a check mark instead of a dot.

Hope this helps.
----- Original Message -----
From: "David Ashley" <dash@xdr.com>
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, December 05, 2002 12:21 PM
Subject: 2.5.40 compile errors with my CONFIG options (included)


> drivers/built-in.o: In function `kd_nosound':
> drivers/built-in.o(.text+0x110b0): undefined reference to `input_event'
> drivers/built-in.o(.text+0x110cd): undefined reference to `input_event'
> drivers/built-in.o: In function `kd_mksound':
> drivers/built-in.o(.text+0x1117a): undefined reference to `input_event'
> drivers/built-in.o: In function `kbd_bh':
> drivers/built-in.o(.text+0x1200a): undefined reference to `input_event'
> drivers/built-in.o(.text+0x12018): undefined reference to `input_event'
> drivers/built-in.o(.text+0x12029): more undefined references to
`input_event' follow
> drivers/built-in.o: In function `kbd_connect':
> drivers/built-in.o(.text+0x1245f): undefined reference to
`input_open_device'
> drivers/built-in.o: In function `kbd_disconnect':
> drivers/built-in.o(.text+0x12477): undefined reference to
`input_close_device'
> drivers/built-in.o: In function `kbd_init':
> drivers/built-in.o(.init.text+0x216e): undefined reference to
`input_register_handler'
[snip]