Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 4152 - emerge system exits at error on xf86Wacom.c
Summary: emerge system exits at error on xf86Wacom.c
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: Lowest normal (vote)
Assignee: Martin Schlemmer (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-25 15:37 UTC by David M. Bourgeois
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Proposed patch for xf86Wacom.c bug. (xf86Wacom.patch,1.33 KB, patch)
2002-07-20 08:54 UTC, Nick Jamieson
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description David M. Bourgeois 2002-06-25 15:37:18 UTC
see the post in the install forum for full details.

I was installing xfree-4.2.0-r12 as part of an emerge system (first-time install).
It barfs in the wacom directory and I applied a workaround of defining
-DLINUX_INPUT. There are  3 other places in the "input" directory tree  (or was that 2),
but they seem to compile fine.

The only thing unusual I can think of was a bunch of X related USE flags I had set, or
perhaps that I am compiling on a K6.
Comment 1 Martin Schlemmer (RETIRED) gentoo-dev 2002-06-28 15:16:44 UTC
Please attatch the log, or at least the link to the forum page.
Comment 2 Nick Jamieson 2002-07-20 08:54:04 UTC
Created attachment 2416 [details, diff]
Proposed patch for xf86Wacom.c bug.
Comment 3 Martin Schlemmer (RETIRED) gentoo-dev 2002-07-20 15:39:15 UTC
I cannot simulate this problem, and still have an idea that it is related in
building with a 2.2 kernel.

Now, this patch may fix things (compile time), but wont it break them when
actually then using xfree compiled with 2.2 kernel on 2.4 kernel ?

If no other way is open but to bootstrap with a 2.2 kernel, the user can still
reboot after "emerge system" to start using a 2.4 kernel *before* merging X.
Comment 4 David M. Bourgeois 2002-07-22 19:28:37 UTC
I believe merging X from a 2.4 kernel boot would be the best solution if
you are in any doubt. Perhaps my USE flags were causing X to be compiled earlier
than I expected (I would expect after you had your gentoo kernel compiled would
be the time for X, but OTOH could it be normal to compile X before the kernel?)

AFAIK, in the 2.2 kernel LINUX_INPUT is not defined, they instead use things
like CONFIG_USB_HID, and a more specific CONFIG_USB_WACOM.

I'm not sure what LINUX_INPUT is supposed to signify, so I can't speak to the
patch.
Comment 5 David M. Bourgeois 2002-07-22 20:30:33 UTC
Hmm, actually my last comment is a bit wrong.

This is .config for a 2.2 kernel:

# USB HID
#
# CONFIG_USB_HID is not set
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_WMFORCE is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

This is .config for a 2.4 kernel:

#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

Things are reorganized (USB --> Input Core).

In another USB section (2.4 kernel) CONFIG_USB_HID and all that (pretty closely)
are set, plus extra USB stuff above and beyond the 2.2 kernel.

But, nowhere in my 2.2 kernel .config could I find CONFIG_INPUT. I'm guessing
the autoconf routine for Xfree finds this in the headers (autoconf.h for a 2.4
kernel) and defines LINUX_INPUT (which apparently only a couple of files use?).
However, for 2.2 kernel header files, it won't find this, and xf86Wacom.c can't
deal with it.

As for the patch, dunno, not being up on USB and HID stuff.
Comment 6 Martin Schlemmer (RETIRED) gentoo-dev 2002-09-08 13:49:44 UTC
This should be fixed in xfree-4.2.1.