From: Justin Pryzby <justinpryzby@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Bug? undefined reference to `input_event'
Date: Thu, 19 Dec 2002 18:47:05 -0500 [thread overview]
Message-ID: <20021219234705.GA11106@perseus.homeunix.net> (raw)
In-Reply-To: <2CC936747EA1284DA378A18D730697420158A56F@exchacad.ms.gettysburg.edu>
Is somebody keeping fixing, or at least keeping track of, these
configuration errors? I've seen a bunch of configuration problems, and
the typical response doesn't include a patch (which is fine, as long as
it ultimately gets fixed). If something can't be configured as a module,
then it shouldn't be possible to configure it as a module.
I can write patches for these things if someone gives me pointers for
how the 2.{4,5} kernel configuration stuff works.
Justin
On Thu, Dec 19, 2002 at 06:39:42PM -0500, Bob Miller wrote:
> On Fri, Dec 20, 2002 at 11:22:09AM +1300, mdew wrote:
> > in both the 2.5.52, and bitkeeper trees, i get this error with make
> > bzImage.
> >
> >
> > Generating include/linux/compile.h (updated)
> > gcc -Wp,-MD,init/.version.o.d -D__KERNEL__ -Iinclude -Wall
> > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> > -pipe -mpreferred-stack-boundary=2 -march=pentium3
> > -Iarch/i386/mach-generic -fomit-frame-pointer -nostdinc -iwithprefix
> > include -DKBUILD_BASENAME=version -DKBUILD_MODNAME=version -c -o
> > init/version.o init/version.c
> > ld -m elf_i386 -r -o init/built-in.o init/main.o init/version.o
> > init/do_mounts.o init/initramfs.o
> > 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
>
> Stuff deleted...
>
> > #
> > # Input device support
> > #
> > CONFIG_INPUT=m
> >
> > #
> > # Userland interfaces
> > #
> > CONFIG_INPUT_MOUSEDEV=m
> > CONFIG_INPUT_MOUSEDEV_PSAUX=y
> > CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
> > CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
> > CONFIG_INPUT_JOYDEV=m
> > # CONFIG_INPUT_TSDEV is not set
> > CONFIG_INPUT_EVDEV=m
> > # CONFIG_INPUT_EVBUG is not set
> >
> > #
> > # Input I/O drivers
> > #
> > # CONFIG_GAMEPORT is not set
> > CONFIG_SOUND_GAMEPORT=y
> > CONFIG_SERIO=y
> > CONFIG_SERIO_I8042=y
> > CONFIG_SERIO_SERPORT=y
> > # CONFIG_SERIO_CT82C710 is not set
> > # CONFIG_SERIO_PARKBD is not set
> >
> > #
> > # Input Device Drivers
> > #
> > CONFIG_INPUT_KEYBOARD=y
> > CONFIG_KEYBOARD_ATKBD=m
> > # CONFIG_KEYBOARD_SUNKBD is not set
> > # CONFIG_KEYBOARD_XTKBD is not set
> > # CONFIG_KEYBOARD_NEWTON is not set
> > # CONFIG_INPUT_MOUSE is not set
> > # CONFIG_INPUT_JOYSTICK is not set
> > # CONFIG_INPUT_TOUCHSCREEN is not set
> > # CONFIG_INPUT_MISC is not set
> >
>
> CONFIG_INPUT and friends can NOT be configed as modules. They must be
> built into the kernel.
>
> --
> 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/
>
next parent reply other threads:[~2002-12-19 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2CC936747EA1284DA378A18D730697420158A56F@exchacad.ms.gettysburg.edu>
2002-12-19 23:47 ` Justin Pryzby [this message]
2002-12-20 0:01 ` Bug? undefined reference to `input_event' Randy.Dunlap
2002-12-19 22:22 mdew
2002-12-19 23:37 ` Bob Miller
2002-12-20 18:11 ` 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=20021219234705.GA11106@perseus.homeunix.net \
--to=justinpryzby@users.sourceforge.net \
--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