Summary: | mesa won't compile in a modular X install | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Wayne <waynetg> |
Component: | New packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | eradicator |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Full output while trying to emerge mesa |
Description
Wayne
2006-07-09 02:33:31 UTC
Created attachment 91262 [details]
Full output while trying to emerge mesa
Looks like your glproto is outdated. *** This bug has been marked as a duplicate of 130174 *** I'm running 1.4.7, there doesn't seem to be anything newer. Should I downgrade? Run this: eselect opengl set --impl-headers xorg-x11, then try again. No luck, everything seems to fail the same way. Try re-merging linux-headers. Also, you should drop the PORTDIR_OVERLAY line from make.conf, since it points to the same place as PORTDIR. No luck I'm afraid :( I faced with this error today when I tried to compile xserver-xorg. The problem is that the selected opengl include belongs to the 32 bit version not to amd64. eselect makes a bad choince. The solution was: 1., Start emerge of xorg-xserver 2., After it writes to console at the begining that it selected xorg-x11 as opengl implementation do what I found in the XGL HowTo: cd /usr/include/GL ln -sf /usr/lib64/opengl/global/include/glext.h glext.h ln -sf /usr/lib64/opengl/xorg-x11/include/gl.h gl.h ln -sf /usr/lib64/opengl/global/include/glxext.h glxext.h ln -sf /usr/lib64/opengl/xorg-x11/include/glx.h glx.h ln -sf /usr/lib64/opengl/xorg-x11/include/glxmd.h glxmd.h ln -sf /usr/lib64/opengl/xorg-x11/include/glxproto.h glxproto.h ln -sf /usr/lib64/opengl/xorg-x11/include/glxtokens.h glxtokens.h So this bug maybe is not the duplicate of bug 130174. My mesa version is: 6.4.2, glproto: 1.4.7 Good call! That did the trick :) Now the next logical question is, where did I go wrong? Is it an eselect bug or did I just mess something up somewhere? Sounds like a possible eselect bug (which may have been filed already). I'll CC Jeremy so he sees this. |