mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Lack of Input-Core causes link errors
Date: Tue, 27 Aug 2002 01:59:57 +0200	[thread overview]
Message-ID: <20020827015957.A26996@ucw.cz> (raw)
In-Reply-To: <3D6AC075.8060007@us.ibm.com>; from haveblue@us.ibm.com on Mon, Aug 26, 2002 at 04:57:41PM -0700

On Mon, Aug 26, 2002 at 04:57:41PM -0700, Dave Hansen wrote:
> Current bk tree won't compile without initcore compiled in.  Adding it 
> makes the link errors go away.  I saw a comment in Linus's changelog about 
> this, is there a fix in progress?
> 
> drivers/built-in.o: In function `kd_nosound':
> drivers/built-in.o(.text+0x1603f): undefined reference to `input_event'
> drivers/built-in.o(.text+0x16058): undefined reference to `input_event'
> drivers/built-in.o: In function `kd_mksound':
> drivers/built-in.o(.text+0x160e7): undefined reference to `input_event'
> drivers/built-in.o: In function `kbd_bh':
> drivers/built-in.o(.text+0x16cca): undefined reference to `input_event'
> drivers/built-in.o(.text+0x16cd8): undefined reference to `input_event'
> drivers/built-in.o(.text+0x16ce9): more undefined references to 
> `input_event' follow
> drivers/built-in.o: In function `kbd_connect':
> drivers/built-in.o(.text+0x170e3): undefined reference to `input_open_device'
> drivers/built-in.o: In function `kbd_disconnect':
> drivers/built-in.o(.text+0x170ff): undefined reference to `input_close_device'
> drivers/built-in.o: In function `kbd_init':
> drivers/built-in.o(.text.init+0x1c57): undefined reference to 
> `input_register_handler'

Yes. Input core will always be built in. (Linus's choice out of other
possible.)

-- 
Vojtech Pavlik
SuSE Labs

      reply	other threads:[~2002-08-26 23:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26 23:57 Dave Hansen
2002-08-26 23:59 ` Vojtech Pavlik [this message]

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=20020827015957.A26996@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=haveblue@us.ibm.com \
    --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

all inboxes | Powered by JetHome®