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
Created attachment 445766 [details] /var/tmp/portage/gnome-extra/polkit-gnome-0.105-r1/temp/build.log
Created attachment 445768 [details] /var/tmp/portage/gnome-extra/polkit-gnome-0.105-r1/work/polkit-gnome-0.105/config.log
Created attachment 445770 [details] emerge --info '=gnome-extra/polkit-gnome-0.105-r1::gentoo'
Created attachment 445772 [details] emerge -pqv '=gnome-extra/polkit-gnome-0.105-r1::gentoo'
Created attachment 445774 [details] /var/tmp/portage/gnome-extra/polkit-gnome-0.105-r1/temp/environment
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?
yes, the problem gone after emerge -1 gtk+
Closing as invalid as current elements suggests system was not properly updated after USE-flag changes.
