emerge --update kdelibs fail with the following error. /bin/sh ../libtool --mode=compile -- tag=CXX g++ -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -I../dcop -I../libltdl -I../kdecore -I../kdeui -I../kio - I../kio/kio -I../kio/kfile -I/usr/qt/3/include -I/usr/X11R6/include -I/usr/kde/3/include - DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG -DNO_DEBUG -O2 -O2 -mcpu=i686 -pipe -fno-exceptions -fno- check-new -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT -c -o libkmid_la.all_cc.lo `test -f libkmid_la.all_cc.cc || echo './'`libkmid_la.all_cc.cc g++ - DHAVE_CONFIG_H -I. -I. -I.. -I./.. -I../dcop -I../libltdl -I../kdecore -I../kdeui -I../kio - I../kio/kio -I../kio/kfile -I/usr/qt/3/include -I/usr/X11R6/include -I/usr/kde/3/include - DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG -DNO_DEBUG -O2 -O2 -mcpu=i686 -pipe -fno-exceptions -fno- check-new -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT -c libkmid_la.all_cc.cc -Wp,-MD,.deps/libkmid_la.all_cc.TPlo -fPIC -DPIC -o .libs/libkmid_la.all_cc.o In file included from libkmid_la.all_cc.cc:9: deviceman.cc:54: sound/asound.h: No such file or directory deviceman.cc:55: sound/asequencer.h: No such file or directory make[2]: *** [libkmid_la.all_cc.lo] Error 1 make[2]: Leaving directory `/var/tmp/portage/kdelibs- 3.0.2/work/kdelibs-3.0.2/libkmid' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/kdelibs-3.0.2/work/kdelibs-3.0.2' make: *** [all] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function kde_src_compile, Line -3988, Exitcode 2 !!! died running emake, kde_src_compile:make ...done! >>> emerge kde-base/kdelibs-3.0.2 to / >>> md5 ;-) kdelibs-3.0.2.tar.bz2 !!! emerge aborting on /usr/portage/kde-base/kdelibs/kdelibs-3.0.2.ebuild .
looks like an arts thingy
Do you have alsa in USE? Do you have alsa installed? Did you have alsa in USE (or at least installed) when you emerged kdelibs the last tmie, and/or when you emerged arts?
Do you have alsa in USE? -no Do you have alsa installed? -yes (parts of it apparently) but it seems as if something is fishy. emerge --update --pretend alsa-lib (no update needed) emerge --pretend alsa-lib ... [ebuild N ] media-sound/alsa-driver-0.9.0_rc2 to / [ebuild R ] media-libs/alsa-lib-0.9.0_rc2 to / What does 'R' mean ? I also have a alsa-lib-0.9.0_rc2 file in /var/cache/edb/dep/media-libs (which i assume has something to do with wheter or not the package is installed) Did you have alsa in USE (or at least installed) when you emerged kdelibs the last tmie, and/or when you emerged arts? -not in use but maybe installed. Jun 18 14:28 /usr/kde/3/lib/libkmid.so -> libkmid.so.0.0.95 Jul 2 08:06 /usr/lib/libasound.so -> libasound.so.2.0. I've have had alsa installed but unmerged it,but somehow it seems as if it didn't get entirely removed. Maybe somethings still need alsa-lib. But why did it allow me do unmerge alsa-driver which alsa-lib obviousle depends on ? rebuilding the alsa-lib and then rebuilding kde-libs proved to be a working workaround.
[R] means Refresh or Remerge, i.e. you already ahve this exact ebuild and version/revision emerged, but since you explicitly requested it it will be emerged again. You have alsa-lib ([R]) but not alsa-drivers ([N]), which is the source of the problem. alsa-lib depends on alsa-drivers. kdelibs depends on alsa-lib (if alsa is in USE) and asumes alsa-drivers is also merged, and fails because it isn't. Although you may not have alsa in USE, our new (as of ~6-8 weeks ago) USE scheme has default USE variables: since alsa-lib is emerged, USE alsa is automatically enabled unless you explicitly disable it (by adding -alsa to your USE line in make.conf). So: if you want alsa support: emerge alsa-lib (pulling in alsa-drivers), optionally put alsa in your USE line to be explicit. If you don't want alsa support: put -alsa in your USE lnie, optionally unmerge alsa-lib to be sure. Then, either way: emerge arts then kdelibs and, to be on the safe side, kdemultimedia too (if you have it emerged).
Why doesn't a update on a component that (obviously) requires alsa-driver either: 1)Complain (Warning: Some required/optional components might not be up-to-date) 2)Fail (and before compiling) 3)Update the required/optional componenents partly present in the system Or maybe rather: When i unmerged alsa-driver i'd like to be able to: 1) know which packages are dependent on this. 2) Be able to a) remerge these packages (if alsa-driver is an optional component) b) unmerge these packages (if alsa-driver is a required component) Is this an problem with emerge or a problem with SBS ? How can i know which things can be added/removed by emerge and which need USE changes ? And if i change USE how do i know what to remerge ? I've tried changing USE in make.conf and doing emerge --pretend --update world but it doesn't tell me anything need updating. I have a too slow computer to do emerge --emptytree world everytime i've added/removed a library/subsystem ;) (I really should give need ASCI white or the Earth Simulator for this tast it should be able to rebuild the entire system in less than one minute) SBS = swedish abbreviation for an error caused by a stupid user and not the system :)
Taking dependency considerations into account when unmerging isn't implemented yet. I don't know when it will be; a search for bugzilla items about it might come up with something.
