Summary: | x11-misc/linuxwacom-0.6.8 won't install due to missing xf86Version.h | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matt Beswick (Soir) <soir> |
Component: | Current packages | Assignee: | X11 External Driver Maintainers <x11-drivers> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alanh, custom_basses, gentoo.org, ikelos, Martin.vGagern, steeeeeveee |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
config.log
Patch for the recent linuxwacom ebuild linuxwacom-0.6.9-xorg-modular.patch linuxwacom-0.7.1.ebuild linuxwacom-0.7.1-xorg-modular.patch linuxwacom-0.7.1-xorg-modular2.patch |
Description
Matt Beswick (Soir)
2005-08-07 13:21:27 UTC
Created attachment 65341 [details]
config.log
!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/linuxwacom-0.6.8/work/linuxwacom-0.6.8/config.log
The situation is the same with linuxwacom-0.6.9. However, after USE=sdk emerge xorg-x11 the following worked USE=sdk emerge linuxwacom hth, s. Thanks, but that doesn't really answer this bug, I feel. Yes, I -could- go off and add SDK useflag for xorg and recompile it and then compile linuxwacom with SDK as well, and in doing so install updated external wacom drivers and then stop using kernel ones, since I might as well. It's an easy way to get an emerged package, sure. (Other bug reports accuse the kernel wacom driver of being out of date anyway. I can believe them. :) ) But if that's all I can do for the functionality of this package, then perhaps linuxwacom shouldn't have the sdk USE flag at all, should always compile drivers as well as userland tools, and should always check for X SDK. Or.. we don't want that, and the configure shouldn't be looking for X SDK if I've asked it not to. I had no special reason to ask it not to apart from not having it in X (because I didn't need it before now) but.. someone might. :) Well, simply, I think it's this: even without the sdk USE flag, this package depends on the SDK. Perhaps USE="sdk" emerge xorg-x11 USE="-sdk" emerge linuxwacom would also get me past the error below. Either X SDK's necessary, or it isn't. And if it is, it probably shouldn't let me get as far as config. (Maybe this is only a minor point now?) ^^ It shouldn't be necessary. I need to figure out some of the autoconf voodoo. I've run into the same problems and none of the above work... I'm just wondering if there are any new developments on this problem... Created attachment 69151 [details, diff]
Patch for the recent linuxwacom ebuild
There where two mistakes in the ebuild.
Now it should not try to build the drivers (and some more tools) if you did not
specified USE=sdk :-)
HTH.
Created attachment 72827 [details, diff]
linuxwacom-0.6.9-xorg-modular.patch
This is another patch, which corrects the location searched to find the
xf86version.h. It should only be applied if the modular xorg has been
installed.
I think it's possible to write some ebuild logic to determine this and apply
the patch under the correct conditions only.
(In reply to comment #7) > Created an attachment (id=72827) [edit] > linuxwacom-0.6.9-xorg-modular.patch > > This is another patch, which corrects the location searched to find the > xf86version.h. It should only be applied if the modular xorg has been > installed. > > I think it's possible to write some ebuild logic to determine this and apply > the patch under the correct conditions only. i applied that patch, but still it can't find xf86Version.h. what part of x(modular) does need to be compiled with sdk flag? checking for valid Xorg SDK... "xf86Version.h missing" configure: error: "Unable to find xf86Version.h under /usr/lib/Server//include and WCM_XORGSDK/xc/include" # locate xf86Version.h || echo ouch! ouch! Yeah, sorry, I rechecked the patch and sure enough it was pretty broken. I'm going to attach a new ebuild (for 0.7.1) and two patches that fix the ./configure scripts attempts to finx xf86Version.h (which by the way should be in /usr/include/xorg for all you modular xorg peoples) and fix the wacom file to include them from the correct location. This ebuild has successfully built for me in the past week, but please note it is ONLY FOR MODULAR X-ORG USERS, and will almost certainly fail to install for <xorg-x11-7.0.0 users. Please note the ebuild also increases the maximum suppression value from 6 to 10 because I seem to get a lot of mouse wobble. This shouldn't affect you, it may even help you. Unfortunately, I still have a lot of mouse wobble... Go figure. Created attachment 73603 [details]
linuxwacom-0.7.1.ebuild
New ebuild.
Created attachment 73604 [details, diff]
linuxwacom-0.7.1-xorg-modular.patch
Patch 1 for ebuild.
Created attachment 73606 [details, diff]
linuxwacom-0.7.1-xorg-modular2.patch
Patch 2 for ebuild.
Updated all ebuilds with the --without-xf86-sdk addition. On a side note, I also added version 0.7.2 to the tree, which I have included modular Xorg support for. *** Bug 127864 has been marked as a duplicate of this bug. *** *** Bug 131004 has been marked as a duplicate of this bug. *** I had the same issue. No release (even the 0.7.2) worked for me. Using the development version (0.7.3-1) with a slightly modified 0.7.2 ebuild worked for me without any problem. I ran into this bug on a stable x86 system. Unmasking x11-misc/linuxwacom-0.7.2 solved the issue for me, while 0.6.7, the latest stable version, still has this bug. I suggest backporting the fix to 0.6.7 or marking 0.7.2 stable. *** Bug 138569 has been marked as a duplicate of this bug. *** This isn't really resolved/fixed is it? Considering the currently marked stable version of linuxwacom doesn't build.. |