Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 372875 - mesa-9999 (in xorg overlay) fails on ./configure with current checkout (gbm)
Summary: mesa-9999 (in xorg overlay) fails on ./configure with current checkout (gbm)
Status: RESOLVED DUPLICATE of bug 372927
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2011-06-24 18:20 UTC by Robin Kauffman
Modified: 2011-06-27 08:12 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Robin Kauffman 2011-06-24 18:20:56 UTC
    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.
Comment 1 Mike MacDonald 2011-06-25 20:18:36 UTC
I can verify this is broken.
Comment 2 nm (RETIRED) gentoo-dev 2011-06-27 08:12:58 UTC

*** This bug has been marked as a duplicate of bug 372927 ***