Summary: | Ubuntu 16.04. Mesa can't be built with specified configurations | ||
---|---|---|---|
Product: | Mesa | Reporter: | Denis <denys.kostin> |
Component: | EGL/Wayland | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED NOTABUG | QA Contact: | mesa-dev |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=106861 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
libwayland-egl1-mesa_installedFiles.png
libwayland-dev_installedFiles.png |
Description
Denis
2018-06-12 15:19:41 UTC
./autogen.sh --with-egl-platforms=x11,wayland --with-gallium-drivers="" --with-dri-drivers=i965 --enable-debug that's how I configured mesa You need to install a newer version of the core Wayland repository, which now provides libwayland-egl. Sorry, Daniel, but have objection. You have mentioned that packet libwayland-egl has to be used. On site https://packages.ubuntu.com/search?keywords=wayland said that packet libwayland-egl is provided by libwayland-egl1-mesa. I have libwayland-egl1-mesa and also libwayland-dev installed. But they both don't have nor package wayland-egl-backend nor header wayland-egl-backend.h (see libwayland-dev_installedFiles.png and libwayland-egl1-mesa_installedFiles.png) So proposed patch is https://patchwork.freedesktop.org/patch/229080/ Created attachment 140143 [details]
libwayland-egl1-mesa_installedFiles.png
Created attachment 140144 [details]
libwayland-dev_installedFiles.png
Sorry, didn't realise at once your words "core Wayland repository". If that means that user has to make Wayland manually or upgrade system to the 18.10 because of lack just only one header, than seems its not issue... such is life, 16.04 won't get a newer wayland, but 18.04 will.. eventually for now, you can use a ppa for a backport with the necessary packaging changes: https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates |
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.