Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
I use KDE, but I want to emerge grip (wich uses several gnome components). I run emerge grip -p and I have a list of gnome-* component. I proceed to emerge and it fails in gnome-mount with this message: (...) checking for x86_64-pc-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GNOME_MOUNT... configure: error: Package requirements (gnome-keyring-1 >= 0.4 libgnomeui-2.0 >= 2.1.5 dbus-glib-1 >= 0.31 hal-storage >= 0.5.7 gtk+-2.0 >= 2.8.0) were not met: No package 'libgnomeui-2.0' 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 GNOME_MOUNT_CFLAGS and GNOME_MOUNT_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/gnome-mount-0.4-r5/work/gnome-mount-0.4/config.log !!! ERROR: gnome-base/gnome-mount-0.4-r5 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 70: Called gnome2_src_configure gnome2.eclass, line 66: Called econf ebuild.sh, line 540: Called die !!! econf failed !!! If you need support, post the topmost build error, and the call stack if relevant.
Created an attachment (id=104725) [details] config.log file As requested in the error, I attach this file.
Created an attachment (id=104726) [details] emerge --info
Already depends on gnome-base/libgnomeui; re-emerge it.
Well, I receive this error during GRP-building on ppc. So something on the dependency seems to be broken.
*** This bug has been marked as a duplicate of bug 147127 *** *** This bug has been marked as a duplicate of bug 147127 ***