I'm trying to build a new LiveCD to begin testing some new functionality for the upcoming 2007.0 release, and gnome-screensaver is failing to build. then mv -f ".deps/gs-grab-x11.Tpo" ".deps/gs-grab-x11.Po"; else rm -f ". deps/gs-grab-x11.Tpo"; exit 1; fi gs-grab-x11.c:33:38: error: X11/extensions/xf86misc.h: No such file or directory gs-grab-x11.c: In function 'xorg_lock_smasher_set_active': gs-grab-x11.c:131: warning: implicit declaration of function 'XF86MiscSetGrabKey sState' gs-grab-x11.c:136: error: 'MiscExtGrabStateAlready' undeclared (first use in thi s function) gs-grab-x11.c:136: error: (Each undeclared identifier is reported only once gs-grab-x11.c:136: error: for each function it appears in.) gs-grab-x11.c:138: error: 'MiscExtGrabStateSuccess' undeclared (first use in this function) gs-grab-x11.c:141: error: 'MiscExtGrabStateLocked' undeclared (first use in this function) make[4]: *** [gs-grab-x11.o] Error 1 make[4]: Leaving directory `/var/tmp/portage/gnome-screensaver-2.16.2/work/gnome-screensaver-2.16.2/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/gnome-screensaver-2.16.2/work/gnome-screensaver-2.16.2/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/tmp/portage/gnome-screensaver-2.16.2/work/gnome-screensaver-2.16.2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-screensaver-2.16.2/work/gnome-screensaver-2.16.2' make: *** [all] Error 2 !!! ERROR: gnome-extra/gnome-screensaver-2.16.2 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1255: Called gnome2_src_compile gnome2.eclass, line 71: Called die !!! compile failure !!! If you need support, post the topmost build error, and the call stack if relevant. Of course, adding x11-proto/xf86miscproto to DEPEND resolves the issue. This is generally not an issue, but since the deps are implicit (it isn't in RDEPEND of any dependencies) it affects us when building with catalyst, as well as users that have only part of GNOME as binary packages, which can easily happen if something along the way failed.
Fixed now. Thanks for the notice :)
No problem. Thanks to you guys for jumping on this stuff so fast.
