Hi- mesa-9999 fails to build currently due to the fact that gbm (the Generic Buffer Manager tracker used largely for Wayland) is automatically enabled in most (not every) configurations, and wants --enable-shared-glapi, which is not enabled by the Mesa ebuild. I simply disabled gbm (--disable-gbm) in the src_configure function (as an option passed to econf directly). Eventually this should be a USE flag, and I'm guessing it's more than possible to build gbm with a largely Gallium-only core (it initially depended on the DRI infrastructure, but my understanding is it now integrates very well with Gallium). If I get an ebuild with a USE flag, I'll submit a patch (right now it forces gbm off for every USE flag set, which is undesirable if the user has enabled 'wayland'). I don't know if Wayland in its current state *requires* gbm, but my guess is it will be a dependency in future so it may not be wise to completely disable the feature. If you require any more information or have concerns with any suggested approach I've mentioned, please don't hesitate to get ahold of me. -Robin K.
I can verify this is broken.
*** This bug has been marked as a duplicate of bug 372927 ***
