compiling x11-libs/qt-3.3.8b-r1 fails with git xextproto headers. Currently, it's not clear where a fix should go. So I propos to at least leave x11-libs/qt-3.3.8-r4 in tree until this is sorted out. some references: a proposed fix: http://lists.freedesktop.org/archives/xorg/2009-January/042653.html a related fix to inputproto: http://cgit.freedesktop.org/xorg/proto/inputproto/commit/?id=b5cbe2d93f6c0129b8f29da97778f6d1b15c38f9 Reproducible: Always Steps to Reproduce: 1. upgrade to git x11 using x11 overlay 2. get qt compiled breaks due to namespace problems (sort of ODR violation) references: a proposed fix: http://lists.freedesktop.org/archives/xorg/2009-January/042653.html a related fix to inputproto: http://cgit.freedesktop.org/xorg/proto/inputproto/commit/?id=b5cbe2d93f6c0129b8f29da97778f6d1b15c38f9
Ok, I just figured qt-3.3.8-r4 fails to compile as well: /usr/include/X11/Xmd.h:137: error: conflicting declaration ‘typedef long int INT32’ ../include/qglobal.h:706: error: ‘INT32’ has a previous declaration as ‘typedef int INT32’ This makes it rather pointless to leave the old ebuild in tree. It's just what happened to be available on my machine. IMO a temporary option would be to have the x11 overlay use the proposed fix.
I pushed the patch from <20090117121713.46bf3332@family.dyweni.com> to xextproto master as commit 7629def0733b82687f2879095451d72e42e13db7. That may be enough to justify a bump to 7.0.6. As a side note, this should not be limited to those using xextproto from git. Before today’s commit, the most recent one was the bump to 7.0.5. Anyone using xextproto-7.0.5 should see the same problem Simon hit.
OK, from what I understand leaving the older qt-3.3.8 ebuild in the tree is not a solution to your problem. And as xextproto-7.0.5 is not in portage yet, regular users won't hit this issue. I will assign this bug to x11 herd, so that they are aware of this issue if and when they plan to add 7.0.5.
Works fine w/updated proto, thanks a lot!
