http://bugs.gentoo.org/show_bug.cgi?id=66223 the eieio() macro gets defined unconditionally in xfree86/common/compiler.h, but it's already defined in <asm/memory.h> for ppc64. affects both HEAD and 6.8.2.
Created attachment 1572 [details] [review] system-eieio-on-ppc64-linux.patch credit to Tim Yamin.
Comment on attachment 1572 [details] [review] system-eieio-on-ppc64-linux.patch build failure for ppc64/linux-2.6 on 6.8.2RC1.
Created attachment 1590 [details] [review] [FIXED_X11R68x] system-eieio-on-ppc64-linux-v2.patch We also need to make sure we're on PPC64, because this breaks PPC32 builds since they lack asm/memory.h.
Comment on attachment 1572 [details] [review] system-eieio-on-ppc64-linux.patch obsoleted...
Comment on attachment 1590 [details] [review] [FIXED_X11R68x] system-eieio-on-ppc64-linux-v2.patch better fix.
Comment on attachment 1590 [details] [review] [FIXED_X11R68x] system-eieio-on-ppc64-linux-v2.patch Approved for commit into X11R6.8.x stable branch in the 2005-01-10 Xorg release-wranglers phone call.
Comment on attachment 1590 [details] [review] [FIXED_X11R68x] system-eieio-on-ppc64-linux-v2.patch Patch checked-in into X11R6.8.x stable branch: /cvs/xorg/xc/ChangeLog,v <-- ChangeLog new revision: 1.365.2.118; previous revision: 1.365.2.117 cvs commit: Using deprecated info format strings. Convert your scripts to use the new argument format and remove '1's from your info file format strings. /cvs/xorg/xc/programs/Xserver/hw/xfree86/common/compiler.h,v <-- compiler.h new revision: 1.3.2.1; previous revision: 1.3 cvs commit: Using deprecated info format strings. Convert your scripts to use the new argument format and remove '1's from your info file format strings. Mailing the commit message to xorg-commit@lists.freedesktop.org...
ajax: Did you commit this patch to Xorg trunk yet ? If "yes" - can this bug be closed ?
woops, i hadn't yet. thanks for the reminder. applied to HEAD, closing.
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.