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 710584 - Fails to build with only the wayland backend enabled
Fails to build with only the wayland backend enabled
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-10-21 20:20 UTC by Emilio Pozuelo Monfort
Modified: 2014-04-28 23:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to move the ifdef's around so that the needed symbols are enabled (628 bytes, patch)
2013-12-29 05:53 UTC, hertz642
none Details | Review

Description Emilio Pozuelo Monfort 2013-10-21 20:20:53 UTC
Building gtk+ master with --enable-wayland-backend --disable-x11-backend fails with:

.libs/libgtk_3_la-gtkapplicationwindow.o: In function `gtk_application_window_real_map':
/home/emilio/src/gnome/gtk+/gtk/gtkapplicationwindow.c:752: undefined reference to `gtk_application_get_menubar_object_path'
/home/emilio/src/gnome/gtk+/gtk/gtkapplicationwindow.c:751: undefined reference to `gtk_application_get_app_menu_object_path'
/usr/bin/ld: .libs/libgtk-3.so.0.1100.0: hidden symbol `gtk_application_get_app_menu_object_path' isn't defined
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status


That's because those symbols are in gtk/gtkapplication.c under #ifdef GDK_WINDOWING_X11
Comment 1 Jens Persson 2013-10-30 19:11:39 UTC
I'm trying to build GTK in the Sailfish SDK, which is Wayland only, and is getting this error too.
Comment 2 hertz642 2013-12-29 05:53:03 UTC
Created attachment 264985 [details] [review]
Patch to move the ifdef's around so that the needed symbols are enabled

Just editing what is enabled/disabled by '#ifdef GDK_WINDOWING_X11' seems to make gtk+-3.10.6 compile fine. I have been able to compile and run various GTK+3 with the changes. I don't know if this will cause any problems with other systems though.
Comment 3 hertz642 2013-12-29 05:54:32 UTC
Pardon, the above should be: "...compile and run various GTK+3 applications with the changes."
Comment 4 Matthias Clasen 2014-04-28 23:18:57 UTC
I just successfully did a wayland-only build, so I guess this was fixed.