Summary: | Mesa 7.10.3 FTBFS (because libdrm?) | ||
---|---|---|---|
Product: | Mesa | Reporter: | Guido Iodice <guido.iodice> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | guido.iodice |
Version: | 7.10 | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Guido Iodice
2011-06-26 02:05:04 UTC
This is not a bug. libdrm >2.4.23 and mesa 7.10.3 just don't go together because of a api change in nouveau. If you really want to try to get it to build together, try including nv04_pushbuf.h in the appropriate locations. http://cgit.freedesktop.org/mesa/drm/commit/?id=45cfb9cf089cd56878b1cb5d15391d2470dbeb7c (In reply to comment #1) > This is not a bug. libdrm >2.4.23 and mesa 7.10.3 just don't go together > because of a api change in nouveau. Well, 7.10.3 requires libdrm >=2.4.24 to build, unless you revert commit "0309089 configure: bump LIBDRM_REQUIRED to 2.4.24" [1], so if mesa isn't supposed to build with libdrm >2.4.23. I wonder, is that commit bogus, or does one part of mesa 7.10.3 require libdrm <=2.4.23 and another libdrm >=2.4.24? [1] http://cgit.freedesktop.org/mesa/mesa/commit/?h=7.10&id=0309089e5a588d829624feaad42d527b010f2a5f Ok, we have a problem here. The patch you mentioned was sent in because of the nouveau api change. I don't know why this ended up in 7.10.3. As far as I can see it *should* be safe to revert this commit. With the libdrm_nouveau experience long behind us, and latest mesa's correctly handling it, I believe we can close this :) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.