After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 706549 - 3.9.12 Configure dies complaining about missing wayland-.. packages
3.9.12 Configure dies complaining about missing wayland-.. packages
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: Wayland
3.9.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-08-22 03:43 UTC by David Ronis
Modified: 2013-08-30 11:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Ronis 2013-08-22 03:43:29 UTC
I'm trying to build gtk+-3.9.12 as part of a from scratch build of gnome 3.9.90.   I get configure errors:

No package 'wayland-client' found
No package 'xkbcommon' found
No package 'wayland-cursor' found

This hasn't happened before (I build every released version of gtk+), althogh I indeed don't have those packages installed.

I added a configure flag:--disable-weyland-backend
but nothing changed.

Have the missing packages been released?
Comment 1 David Ronis 2013-08-22 03:52:23 UTC
I think I figured out what I was doing wrong.  First, it's --disable-wayland-backend (not weyland), and with this I got a configure error saying that no backends were selected.  Adding --enable-x11-backend fixes the problem.  Shouldn't all this be auto-detected?
Comment 2 David Ronis 2013-08-22 04:40:52 UTC
The problem resurfaces later in the build: 

CC       libgtk_3_la-gtkclipboard-wayland.lo
In file included from ../gdk/wayland/gdkwayland.h:32:0,
                 from gtkclipboard-waylandprivate.h:21,
                 from gtkclipboard-wayland.c:24:
../gdk/wayland/gdkwaylanddevice.h:27:28: fatal error: wayland-client.h: No such file or directory
 #include <wayland-client.h>

 I have --disable-wayland-backend set in configure, so why is this being build in the 1st place?
Comment 3 Matthias Clasen 2013-08-23 19:44:46 UTC
I just tried building with either the wayland or x11 backends disabled, and found it to work. Haven't tried with missing dependencies, though.
Comment 4 David Ronis 2013-08-23 20:22:35 UTC
It works here too if I manually disable the #include <wayland-client.h>.
Comment 5 Rob Bradford 2013-08-27 13:16:58 UTC
I think this was fixed by: 

commit ec26a909f69e12dee1d151c8795f62d794fe7b24
Author: Saleem Abdulrasool <compnerd@compnerd.org>
Date:   Tue Aug 20 19:30:05 2013 -0700

    clipboard: fix build without wayland
    
    Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org>
Comment 6 Heather 2013-08-30 10:52:08 UTC
Thanks for this find,

I apply this patch : https://git.gnome.org/browse/gtk+/patch/?id=ec26a909f69e12dee1d151c8795f62d794fe7b24

And then get:

Making all in uite
/bin/sh: line 20: cd: uite: No such file or directory

T_T
Comment 7 Heather 2013-08-30 11:11:34 UTC
Ah sorry it was broken by my own sctipt.