On a newly installed system I got the following error at what I think is the end of the xfree-4.2.0-r2 build. Here is the last bit of output: ========================================================================= Full build of Release 6.6 of the X Window System complete. /usr/sbin/ebuild.sh: xmkmf: command not found make: *** No targets specified and no makefile found. Stop. !!! ERROR: The ebuild did not complete successfully. !!! Function src_complie, Line 7, Exitcode 2 !!! (no error message) !! emerge aborting on /usr/portage/x11-base/xfree/xfree-4.2.0-r2.ebuild . ========================================================================= Looking at the relavent code in xfree-4.2.0-r2.ebuild I'd say the ebuild author didn't consider that xmkmf won't be installed until xfree install successfully. I tried changing 'xmkmf' to '../../config/util/xmkmf' but that fails with 'imake: command not found'. I'm gonna guess you need to alter the path a bit or wait until after a successful install of xfree to install the glxinfo stuff. I only downloaded Gentoo yesterday so I'm not sure how best to fix this yet.
until cvs.gentoo.org is available again, here is a fix to be able to emerge 4.2; comment the 4 lines after #build glxinfo the comment the 3 lines after #install glxinfo in the xfree-4.2.0-r2.ebuild file
my workaround for this was having xfree-4.1.0 already installed, and adding /usr/X11R6/bin to my path before emerging. however, even with having imake and xmkmf already installed, i still hit a snag. when compiling glxinfo, the build was aborted due to an error from ld. it was unable to find -lGLU. i merged mesa-glu and tried rebuilding glxinfo, this time with success. is this my own unique problem, or does glxinfo depend on mesa-glu? shouldn't xfree provide it's own libGLU.so, or will a new dependancy be added to the xfree ebuild?
Sorry guys, forgot xmkmf would not be availeble, and since I had 4.1.0 installed, it worked fine. This was supposed to be fixed on CVS about an hour after the commit (gentoo user report .. sorry, forgot who it was), but seems CVS and RSYNC already didnt talk to each other :(
Ok, CVS is up, so an emerge rsync should fix this.
