Bug 593842 – gnome-extra/polkit-gnome-0.105-r1 Package requirements (gtk+-3.0 >= 3.0.0) were not met

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Arsen Shnurkov 2016-09-15 06:29:54 UTC]

checking for GTK... no
configure: error: Package requirements (gtk+-3.0 >= 3.0.0) were not met:

Package 'wayland-egl', required by 'gdk-3.0', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GTK_CFLAGS
and GTK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

Reproducible: Always

[Comment 1 Arsen Shnurkov 2016-09-15 06:31:21 UTC]

Created attachment 445766 [details]
/var/tmp/portage/gnome-extra/polkit-gnome-0.105-r1/temp/build.log

[Comment 2 Arsen Shnurkov 2016-09-15 06:32:28 UTC]

Created attachment 445768 [details]
/var/tmp/portage/gnome-extra/polkit-gnome-0.105-r1/work/polkit-gnome-0.105/config.log

[Comment 3 Arsen Shnurkov 2016-09-15 06:33:43 UTC]

Created attachment 445770 [details]
emerge --info '=gnome-extra/polkit-gnome-0.105-r1::gentoo'

[Comment 4 Arsen Shnurkov 2016-09-15 06:35:46 UTC]

Created attachment 445772 [details]
emerge -pqv '=gnome-extra/polkit-gnome-0.105-r1::gentoo'

[Comment 5 Arsen Shnurkov 2016-09-15 06:36:57 UTC]

Created attachment 445774 [details]
/var/tmp/portage/gnome-extra/polkit-gnome-0.105-r1/temp/environment

[Comment 6 Mart Raudsepp 2016-09-15 07:14:49 UTC]

You have somehow managed to break your gtk+ by building it against wayland with USE=wayland, and then somehow losing wayland-egl pkgconfig package (/usr/lib/pkgconfig/wayland-egl.pc). I recall such an issue happening for someone before, but I can't find it to mark duplicate against.
I wonder how such a situation could have happened with gtk+[wayland] depending on mesa[wayland], which provides that wayland-egl. You don't have USE=wayland right now, so you must have had it before, or it somehow automatically started depending on it.

Did you have USE=wayland in the past, now have removed it, but only rebuild mesa and somehow skipped gtk+ rebuild with --newuse and it somehow allowed to do this?

[Comment 7 Arsen Shnurkov 2016-09-15 07:44:29 UTC]

yes, the problem gone after 
emerge -1 gtk+

[Comment 8 Gilles Dartiguelongue (RETIRED) 2016-10-15 08:49:35 UTC]

Closing as invalid as current elements suggests system was not properly updated after USE-flag changes.