blah, blah, blah ... checking for dcgettext... yes checking for gmsgfmt... /usr/bin/gmsgfmt checking for xgettext... /usr/bin/xgettext checking for gconftool-2... /usr/bin/gconftool-2 Using config source xml::/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for GDU_MODULE_VERSION_CHECK... Package gnome-doc-utils was not found in the pkg-config search path. Perhaps you should add the directory containing `gnome-doc-utils.pc' to the PKG_CONFIG_PATH environment variable No package 'gnome-doc-utils' found configure: error: Package requirements (gnome-doc-utils >= 0.3.2) were not met: Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GDU_MODULE_VERSION_CHECK_CFLAGS and GDU_MODULE_VERSION_CHECK_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/gcalctool-5.8.16/work/gcalctool-5.8.16/config.log !!! ERROR: gnome-extra/gcalctool-5.8.16 failed. Call stack: ebuild.sh, line 1539: Called dyn_compile ebuild.sh, line 939: Called src_compile ebuild.sh, line 1248: Called gnome2_src_compile gnome2.eclass, line 63: Called gnome2_src_configure gnome2.eclass, line 59: Called econf '--disable-gtk-doc' ebuild.sh, line 541: Called die !!! econf failed !!! If you need support, post the topmost build error, and the call stack if relevant. emerging 'gnome-doc-utils' solved the above problem.
*** Bug 140198 has been marked as a duplicate of this bug. ***
What's keeping this? This is stable on x86..
I don't use WindowMaker and gcalctool seems to need app-text/gnome-doc-utils package. So I simply did : emerge gnome-doc-utils gcalctool
thanks, in cvs for 2.14.3
John, the fixed version is not stable on x86. We should either fix the stable 5.8.16 as well or stabilize 5.8.20.
it will be requested stable shortly.
*** Bug 144632 has been marked as a duplicate of this bug. ***