From: "Richard B. Tilley " "(Brad)" <rtilley@vt.edu>
To: Bob Miller <rem@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.52 compile error
Date: 17 Dec 2002 16:27:40 -0500 [thread overview]
Message-ID: <1040160460.17548.20.camel@oubop4.bursar.vt.edu> (raw)
In-Reply-To: <20021217211618.GB1069@doc.pdx.osdl.net>
[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]
CONFIG_INPUT is modular, do I *have* to build it in inorder to compile?
On Tue, 2002-12-17 at 16:16, Bob Miller wrote:
> On Tue, Dec 17, 2002 at 03:57:01PM -0500, rtilley wrote:
> > Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps
> > returning this error on 2 totally different x86 PCs:
> >
> >
> > drivers/built-in.o: In function `kd_nosound':
> > drivers/built-in.o(.text+0x1883f): undefined reference to `input_event'
> > drivers/built-in.o(.text+0x18861): undefined reference to `input_event'
> > drivers/built-in.o: In function `kd_mksound':
> > drivers/built-in.o(.text+0x1890a): undefined reference to `input_event'
> > drivers/built-in.o: In function `kbd_bh':
> > drivers/built-in.o(.text+0x197a2): undefined reference to `input_event'
> > drivers/built-in.o(.text+0x197c1): undefined reference to `input_event'
> > drivers/built-in.o(.text+0x197e0): more undefined references to `input_event'
> > follow
> > drivers/built-in.o: In function `kbd_connect':
> > drivers/built-in.o(.text+0x19d54): undefined reference to `input_open_device'
> > drivers/built-in.o: In function `kbd_disconnect':
> > drivers/built-in.o(.text+0x19d7f): undefined reference to `input_close_device'
> > drivers/built-in.o: In function `kbd_init':
> > drivers/built-in.o(.init.text+0x12c1): undefined reference to
> > `input_register_handler'
> > make: *** [.tmp_vmlinux1] Error 1
> >
> >
> > Where is the fix for this?
> >
> At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support"
> off the main page.
>
> --
> Bob Miller Email: rem@osdl.org
> Open Source Development Lab Phone: 503.626.2455 Ext. 17
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-12-17 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 20:57 rtilley
2002-12-17 21:16 ` Bob Miller
2002-12-17 21:27 ` Richard B. Tilley (Brad) [this message]
2002-12-17 21:29 ` Steven Cole
2002-12-17 21:34 ` Richard B. Tilley (Brad)
2002-12-17 22:49 ` James Simmons
2002-12-18 7:00 ` eric lin
2002-12-17 23:03 ` Randy.Dunlap
2002-12-18 6:39 ` eric lin
2002-12-17 22:54 ` Bob Miller
2002-12-18 7:26 ` eric lin
2002-12-17 23:28 ` Randy.Dunlap
2002-12-18 7:46 ` eric lin
2002-12-18 13:12 Philippe Gramoullé
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=1040160460.17548.20.camel@oubop4.bursar.vt.edu \
--to=rtilley@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rem@osdl.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
all inboxes | Powered by JetHome®