gdm doesn't have depend on gnome-keyrings So, "emerge gdm" leads to error when gnome-keyrings is not installed.
no it doesn't, it doesn't need gnome-keyring. Again this is a completely useless bugreport, it misses _any_ evidence and obviously contains completely wrong info. Give us relevant info (output, your 'emerge info', etc) then we might be able to check out what might be the problem here. And read the freaking bugreport form, it tries to explain what you need to do to make a somewhat useful bugreport, but obviously you couldn't be bothered to do so.
Sorry, there is additional info to my bug report. I've just repeated the problem: epm -e gnome-keyring USE="-tcpd" ACCEPT_KEYWORDS=~x86 emerge -v gdm /bin/sh ../libtool --mode=link gcc -mcpu=athlon -march=athlon -O2 -pipe -fomit-frame-pointer -Wall -Wmissing-prototypes -o test-ve-config test-ve-config.o -Wl,--export-dynamic -pthread -L/usr/X11R6/lib -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnomecanvas-2 -lgnome-2 -lpopt -lart_lgpl_2 -lpangoft2-1.0 -lbonobo-2 -lgconf-2 -lgnomevfs-2 -lbonobo-activation -lORBit-2 -lgthread-2.0 -lglade-2.0 -lgtk-x11-2.0 -lxml2 -lpthread -lz -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -L../vicious-extensions -lvicious mkdir .libs libtool: link: cannot find the library `/usr/lib/libgnome-keyring.la' make[3]: *** [test-ve-config] Error 1 make[3]: Leaving directory `/portage_tmp/portage/gdm-2.4.4.7-r1/work/gdm-2.4.4.7/vicious-extensions' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/portage_tmp/portage/gdm-2.4.4.7-r1/work/gdm-2.4.4.7/vicious-extensions' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/portage_tmp/portage/gdm-2.4.4.7-r1/work/gdm-2.4.4.7' make: *** [all-recursive-am] Error 2 !!! ERROR: gnome-base/gdm-2.4.4.7-r1 failed. !!! Function gnome2_src_compile, Line 39, Exitcode 2 !!! compile failure
there is "emerge info" output: Portage 2.0.50-r2 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2.4.20-gentoo-r5) ================================================================= System uname: 2.4.20-gentoo-r5 i686 AMD Duron(tm) Processor Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.58 Automake: sys-devel/automake-1.7.8 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon -march=athlon -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon -march=athlon -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/portage_tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow alsa apm avi berkdb cdr crypt cups encode esd faad foomaticdb gdbm gif gnome gtk gtk2 guile jpeg libg++ libwww mad mikmod mmx mozilla moznocompose moznoirc moznomail mpeg ncurses nls oggvorbis opengl pam pdflib pic png postgres quicktime readline sdl slang spell ssl tcpd truetype x86 xml2 xv zlib"
Info added, so I reopen the bug. There is a need to test if problem arise on default installation (without gnome). If there is no such problem, then it's only my fault and bug is invalid. (In this case to avoid such bugreports we need to add dependency tracking on package deletion. But it's another story .)
you shouldnt just randomly remove packages, ofcourse it breaks. This is no mistake, you should just not touch that.
ok
