From: rtilley <rtilley@vt.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.5.52 compile error
Date: Tue, 17 Dec 2002 15:57:01 -0500 [thread overview]
Message-ID: <3E058049@zathras> (raw)
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?
next reply other threads:[~2002-12-17 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 20:57 rtilley [this message]
2002-12-17 21:16 ` 2.5.52 compile error Bob Miller
2002-12-17 21:27 ` Richard B. Tilley (Brad)
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
-- strict thread matches above, loose matches on Subject: below --
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=3E058049@zathras \
--to=rtilley@vt.edu \
--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