checking for a useful monotonic clock ...... yes checking for XLIB... yes checking for GL... configure: error: Package requirements (glproto >= 1.4.9 gl >= 7.1.0) were not met: Package xxf86vm was not found in the pkg-config search path. Perhaps you should add the directory containing `xxf86vm.pc' to the PKG_CONFIG_PATH environment variable Package 'xxf86vm', required by 'gl', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GL_CFLAGS and GL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. -------------------------------------------------------------------- After compiling libXxf86vm, which wasn't installed, xorg-server compiled ok. Please add the dependency check to the ebuild file. Reproducible: Always
xorg-server, if !minimal, depends on mesa, mesa depends on x11-libs/libXxf86vm. Looks like something was wrong on your side.
So what do you mean? If I get what you're saying, it is wrong on mesa? media-libs/mesa-7.5.2 So what, this version of mesa didn't need libXx86vm? Perhaps the new xorg-server should also be pulling a newer mesa then? Best regards
media-libs/mesa-7.5.2 was removed from the tree on 3rd August. Seems you're not updating your system correctly.
Indeed, I am not. Still, can anything be done to make upgrades less painful? I'm guessing that this version of xorg-server doesn't need the more recent mesa but needs that particular lib, so either it must pull the most recent version or xorg-server should. Do you agree there is a bug with dependencies or are you saying that it isn't one? Best regards, Tiago
Unless I'm missing something, a standard 'emerge -upvD world' should have picked up a recent, still in-tree mesa.
Right, but what if I just wanted a more recent xorg-server package? I mean, I don't do an emerge world every week - I stopped doing that when it proved it was an infeasible practice, prone to general breakage of one's system. Best regards
'-D' should work for any package, at least in cases as this one.
Since '-D' isn't the default behavior of portage, isn't this a bug? The problem is solved for me but someone may stumble on it. I've seen too many problems like these all over the tree. Best regards
