Summary: | piglit_drm_dma_buf.c:265:12: error: ‘GBM_FORMAT_R8’ undeclared | ||
---|---|---|---|
Product: | piglit | Reporter: | Vinson Lee <vlee> |
Component: | tests | Assignee: | Piglit Mailing List <piglit> |
Status: | RESOLVED FIXED | QA Contact: | Piglit Mailing List <piglit> |
Severity: | normal | ||
Priority: | medium | CC: | baker.dylan.c, jv356 |
Version: | unspecified | Keywords: | bisected, regression |
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Include gbm even without gbm_bo_map
cmake: Reintroduce version check to gbm_bo_map check |
Description
Vinson Lee
2017-06-08 21:21:02 UTC
Created attachment 131826 [details] [review] Include gbm even without gbm_bo_map Does this patch help? (In reply to Jan Vesely from comment #1) > Created attachment 131826 [details] [review] [review] > Include gbm even without gbm_bo_map > > Does this patch help? No. Created attachment 131841 [details] [review] cmake: Reintroduce version check to gbm_bo_map check new patch. it reintroduces the old check so PIGLIT_HAS_GBM_BO_MAP is only defined if both vesion >= 12.1 AND the function is available (In reply to Jan Vesely from comment #3) > Created attachment 131841 [details] [review] [review] > cmake: Reintroduce version check to gbm_bo_map check > > new patch. it reintroduces the old check so PIGLIT_HAS_GBM_BO_MAP is only > defined if both vesion >= 12.1 AND the function is available This patch fixes the build for me. Tested-by: Vinson Lee <vlee@freedesktop.org> commit ae373e3d56159a3f371deed6c6796bb1ba887364 Author: Jan Vesely <jano.vesely@gmail.com> Date: Sat Jun 10 14:31:55 2017 +0200 cmake: Reintroduce version check to gbm_bo_map check Fixes: 2217871ac937 ("CMake: define GBM_BO_MAP only when symbol is found") Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101358 Signed-off-by: Jan Vesely <jano.vesely@gmail.com> Tested-by: Vinson Lee <vlee@freedesktop.org> |
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.