Public bug reported: lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04
# apt-cache policy libgtk-3-dev libgtk-3-dev: Installed: 3.18.9-1ubuntu3.1 Candidate: 3.18.9-1ubuntu3.1 Version table: *** 3.18.9-1ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.18.9-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages This bug (see Bug #1106188) has re-emerged on arm64: pkg-config gtk+-3.0 --cflags Package wayland-egl was not found in the pkg-config search path. Perhaps you should add the directory containing `wayland-egl.pc' to the PKG_CONFIG_PATH environment variable Package 'wayland-egl', required by 'gtk+-3.0', not found This affects both gtk and gdk. I edited gdk-3.0.pc and gtk-3.0.pc to remove any references to wayland or mir, and it seems to be working. I am not sure how exactly these packages can provide the correct cflags, because they may not know their backend until runtime. Can we just remove the requirement for wayland, mir and x11? ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: lsb_release -rd - Description: Ubuntu 16.04.1 LTS - Release: 16.04 + Description: Ubuntu 16.04.1 LTS + Release: 16.04 - Installed: 3.18.9-1ubuntu3.1 - Candidate: 3.18.9-1ubuntu3.1 - Version table: - *** 3.18.9-1ubuntu3.1 500 - 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 Packages - 100 /var/lib/dpkg/status - 3.18.9-1ubuntu3 500 - 500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages - + # apt-cache policy libgtk-3-dev + libgtk-3-dev: + Installed: 3.18.9-1ubuntu3.1 + Candidate: 3.18.9-1ubuntu3.1 + Version table: + *** 3.18.9-1ubuntu3.1 500 + 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 Packages + 100 /var/lib/dpkg/status + 3.18.9-1ubuntu3 500 + 500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages This bug (see Bug #1106188) has re-emerged on arm64: - pkg-config gtk+-3.0 --cflags - Package wayland-egl was not found in the pkg-config search path. - Perhaps you should add the directory containing `wayland-egl.pc' - to the PKG_CONFIG_PATH environment variable - Package 'wayland-egl', required by 'gtk+-3.0', not found + pkg-config gtk+-3.0 --cflags + Package wayland-egl was not found in the pkg-config search path. + Perhaps you should add the directory containing `wayland-egl.pc' + to the PKG_CONFIG_PATH environment variable + Package 'wayland-egl', required by 'gtk+-3.0', not found + This affects bot gtk and gdk. I edited gdk-3.0.pc and gtk-3.0.pc to + remove any references to wayland or mir, and it seems to be working. - This affects bot gtk and gdk. I edited gdk-3.0.pc and gtk-3.0.pc to remove any references to wayland or mir, and it seems to be working. - - - I am not sure how exactly these packages can provide the correct cflags, because they may not know their backend until runtime. Otherwise perhaps several versions of gtk can be produces for each backend, similar to wxgtk vs wxqt or....? + I am not sure how exactly these packages can provide the correct cflags, + because they may not know their backend until runtime. Otherwise + perhaps several versions of gtk can be produces for each backend, + similar to wxgtk vs wxqt or....? ** Description changed: lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 - # apt-cache policy libgtk-3-dev - libgtk-3-dev: + # apt-cache policy libgtk-3-dev + libgtk-3-dev: Installed: 3.18.9-1ubuntu3.1 Candidate: 3.18.9-1ubuntu3.1 Version table: *** 3.18.9-1ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.18.9-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages This bug (see Bug #1106188) has re-emerged on arm64: pkg-config gtk+-3.0 --cflags Package wayland-egl was not found in the pkg-config search path. Perhaps you should add the directory containing `wayland-egl.pc' to the PKG_CONFIG_PATH environment variable Package 'wayland-egl', required by 'gtk+-3.0', not found - This affects bot gtk and gdk. I edited gdk-3.0.pc and gtk-3.0.pc to + This affects both gtk and gdk. I edited gdk-3.0.pc and gtk-3.0.pc to remove any references to wayland or mir, and it seems to be working. I am not sure how exactly these packages can provide the correct cflags, - because they may not know their backend until runtime. Otherwise - perhaps several versions of gtk can be produces for each backend, - similar to wxgtk vs wxqt or....? + because they may not know their backend until runtime. Can we just + remove the requirement for wayland, mir and x11? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1615160 Title: Unable to build any GTK app, because of missing wayland-client.pc Status in gtk+3.0 package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 # apt-cache policy libgtk-3-dev libgtk-3-dev: Installed: 3.18.9-1ubuntu3.1 Candidate: 3.18.9-1ubuntu3.1 Version table: *** 3.18.9-1ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.18.9-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages This bug (see Bug #1106188) has re-emerged on arm64: pkg-config gtk+-3.0 --cflags Package wayland-egl was not found in the pkg-config search path. Perhaps you should add the directory containing `wayland-egl.pc' to the PKG_CONFIG_PATH environment variable Package 'wayland-egl', required by 'gtk+-3.0', not found This affects both gtk and gdk. I edited gdk-3.0.pc and gtk-3.0.pc to remove any references to wayland or mir, and it seems to be working. I am not sure how exactly these packages can provide the correct cflags, because they may not know their backend until runtime. Can we just remove the requirement for wayland, mir and x11? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1615160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
