Opened 9 years ago
Closed 9 years ago
#7486 closed enhancement (fixed)
libva-intel-driver does not build without Wayland
| Reported by: | Chris Staub | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.10 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
Wayland is supposed to be optional for libva-intel-driver, but the configure for the driver actually errors out if wayland-scanner is not found, even if Wayland is explicitly disabled. After searching I found this - https://bugs.freedesktop.org/show_bug.cgi?id=79478 - and apparently the issue appears to be in the autotools used to create configure, as recreating it with "autoreconf -iv" allows configure to continue without wayland-scanner. I've tested this and it does work - after using autoreconf, libva-intel-driver does configure and build without Wayland installed.
Therefore, until there is a release that fixes this issue (the final comment in the bug report seems to indicate it has been patched upstream) I suggest adding autoreconf before the configure command for libav-intel-driver, for it to work without Wayland.
Change History (3)
comment:1 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
Chris, I can restore the 'autoreconf -iv' command, but the freedesktop link you provide indicates the problem should be fixed. Did you test with version 1.6.3?
That version should have fixed the problem. I didn't see any issues because I built Wayland for Mesa since I knew it was needed for Plasma.