Summary: | build error on arm64: tegra_screen.c:33: /usr/include/xf86drm.h:41:10: fatal error: drm.h: No such file or directory | ||
---|---|---|---|
Product: | Mesa | Reporter: | Fabio Pedretti <pedretti.fabio> |
Component: | Other | Assignee: | mesa-dev |
Status: | VERIFIED FIXED | QA Contact: | mesa-dev |
Severity: | major | ||
Priority: | medium | CC: | fdo-bugs, vlee |
Version: | git | ||
Hardware: | ARM | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Fabio Pedretti
2019-02-15 18:19:53 UTC
*** Bug 109647 has been marked as a duplicate of this bug. *** @Eric Engestrom: any news on this build issue? Sorry, I broke two libdrm things within a few days and I got confused between the issues. Looking at this one now, but at first glance it looks like src/gallium/drivers/tegra/meson.build is just missing its dep_libdrm. @Fabio could you test this for me? ----8<---- diff --git a/src/gallium/drivers/tegra/meson.build b/src/gallium/drivers/tegra/meson.build index d24438edc1383d571552..939d6294601cd07b3f51 100644 --- a/src/gallium/drivers/tegra/meson.build +++ b/src/gallium/drivers/tegra/meson.build @@ -33,6 +33,7 @@ libtegra = static_library( inc_include, inc_src, inc_gallium, inc_gallium_aux, inc_gallium_drivers, inc_gallium_winsys, ], + dependencies : dep_libdrm, ) driver_tegra = declare_dependency( ---->8---- Instead of testing a copy/pasted patch, you can test the branch in this MR: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/270 Fixed by: commit b787403a21de8eeb21336274ba6ff19392a216da Author: Eric Engestrom <eric.engestrom@intel.com> Date: Tue Feb 19 10:57:58 2019 +0000 tegra/meson: add missing dep_libdrm Fixes: f1374805a86d0d506557 "drm-uapi: use local files, not system libdrm" Bug: https://bugs.freedesktop.org/show_bug.cgi?id=109645 Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> |
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.