Summary: | x11-apps/xrandr-1.2.2 fails to compile on uclibc Gentoo system | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Marc Blumentritt <marc.blumentritt> | ||||||||
Component: | App/xrandr | Assignee: | Keith Packard <keithp> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | jesserayadkins, mat, rmh3093, yann | ||||||||
Version: | 7.2 (2007.02) | ||||||||||
Hardware: | x86 (IA32) | ||||||||||
OS: | Linux (All) | ||||||||||
URL: | http://bugs.gentoo.org/show_bug.cgi?id=197013 | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Marc Blumentritt
2007-10-26 06:48:12 UTC
Created attachment 12214 [details] [review] xrandr-1.2.2-clone-nameclash.patch Here is the patch from: http://bugs.gentoo.org/show_bug.cgi?id=197013 Regards, Marc its 2009 now... a year and a half later and this bug still not resolved... why cant this symbol get renamed so that things compile? Created attachment 30953 [details] [review] Use a prefix for enum type _policy and _relation like other enums in xrandr.c Here's patch which rewrote two enums to match what's done for others enum in the sources. Created attachment 30956 [details] [review] Disable --clone / --extend support code. This is another way to fix the problem: the code using enum clone constant is not used, so it can be disabled. A bug report was created against uClibc. See https://bugs.busybox.net/show_bug.cgi?id=727 Thanks to Matthias Hopf from SuSe, a patch with a workaround against the uClibc related bug was added to xrandr. See http://cgit.freedesktop.org/xorg/app/xrandr/commit/?id=5f7d052d63875f059f5693c68ee9fdf559ad5300 (In reply to comment #6) > Thanks to Matthias Hopf from SuSe, a patch with a workaround against the uClibc > related bug was added to xrandr. > See > http://cgit.freedesktop.org/xorg/app/xrandr/commit/?id=5f7d052d63875f059f5693c68ee9fdf559ad5300 Closing as FIXED. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.