Re: compile error in pre7-ac2: usb & input

[Vojtech Pavlik]

On Fri, Sep 20, 2002 at 05:27:10PM +1000, Brad Hards wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Fri, 20 Sep 2002 17:09, Vojtech Pavlik wrote:
> > On Fri, Sep 20, 2002 at 07:09:20AM +1000, Brad Hards wrote:
> > > On Thu, 19 Sep 2002 23:54, Vojtech Pavlik wrote:
> > > > On Thu, Sep 19, 2002 at 04:04:08PM +0300, Meelis Roos wrote:
> > > > > drivers/usb/usbdrv.o: In function `hidinput_hid_event':
> > > > > drivers/usb/usbdrv.o(.text+0x11573): undefined reference to
> > > > > `input_event' drivers/usb/usbdrv.o(.text+0x115ee): undefined
> > > > > reference to `input_event' drivers/usb/usbdrv.o(.text+0x11600):
> > > > > undefined reference to `input_event'
> > > > > drivers/usb/usbdrv.o(.text+0x11641): undefined reference to
> > > > > `input_event' drivers/usb/usbdrv.o(.text+0x11664): undefined
> > > > > reference to `input_event' drivers/usb/usbdrv.o(.text+0x11682): more
> > > > > undefined references to `input_event' follow drivers/usb/usbdrv.o: In
> > > > > function
> > > > > `hidinput_connect':
> > > > > drivers/usb/usbdrv.o(.text+0x118d4): undefined reference to
> > > > > `input_register_device' drivers/usb/usbdrv.o: In function
> > > > > `hidinput_disconnect':
> > > > > drivers/usb/usbdrv.o(.text+0x118f3): undefined reference to
> > > > > `input_unregister_device'
> > > >
> > > > Well, you enabled HID as built-in and Input as modular. HID needs
> > > > Input.
> > >
> > > Not quite. CONFIG_USB + CONFIG_USB_HIDDEV doesn't need input.
> > > Unfortunately CONFIG_USB_HIDINPUT does, and it is a dep_bool.
> > > The only clean way I can see is to build HID as three seperate modules -
> > > a core, the input interface, and the hiddev interface.  Even that is
> > > pretty ugly.
> >
> > More modules, oh no!
> Hmmm. You could always build part of the input layer into the kernel 
> unconditionally (like the old keyboard handling code?). Not nice on some 
> embedded applications, though you could probably build an "input.o" that is a 
> bit smaller.
> Or a version of the "unconditional build" based on some setup determined after 
> the config step.
> I'm still looking for a better idea - got any?

As of current 2.5 input.o is always built in. (Since CONFIG_INPUT is defined to Y).

-- 
Vojtech Pavlik
SuSE Labs