On Tue, 2005-10-11 at 22:01 +0100, Jorge Almeida wrote: > java hates me. > > [EMAIL PROTECTED] ~ $ revdep-rebuild -p > > Checking reverse dependencies... > Packages containing binaries and libraries broken by any package update, > will be recompiled. > > Collecting system binaries and libraries... done. > (/root/.revdep-rebuild.1_files) > > Collecting complete LD_LIBRARY_PATH... done. > (/root/.revdep-rebuild.2_ldpath) > > Checking dynamic linking consistency... > broken /opt/blackdown-jdk-1.4.2.02/jre/lib/i386/libjsoundalsa.so > (requires libasound.so.2) > done. > (/root/.revdep-rebuild.3_rebuild) > > Assigning files to ebuilds... done. > (/root/.revdep-rebuild.4_ebuilds) > > Evaluating package order... done. > (/root/.revdep-rebuild.5_order) > > All prepared. Starting rebuild... > emerge --oneshot --nodeps -p > =dev-java/blackdown-jdk-1.4.2.02 > > These are the packages that I would merge, in order: > > Calculating dependencies ...done! > [ebuild R ] dev-java/blackdown-jdk-1.4.2.02 > Now you can remove -p (or --pretend) from arguments and > re-run revdep-rebuild. > > I already reemerged dev-java/blackdown-jdk, which is the only java > installed, and didn't forget to env-update and source /etc/profile. > Running revdep-rebuild is useless, as a second revdep-rebuild -p will > still give the same error message. > > And why should something named > /opt/blackdown-jdk-1.4.2.02/jre/lib/i386/libjsoundalsa.so exist? I don't > have the "alsa" USE flag set, for the excelent reason that this is an > office workstation with no sound equipment whatsoever. > Could it be that somehow the ebuild is ignoring this point? > I unset "browserplugin" before emerging, just in case this was pulling > sound support. Still, "mozilla" was set; the emerge says that the former > USE variable is the latter renamed... > > What to do? Can I safely ignore the revdep-rebuild messages? I think you can safely ignore that (unless you're running java applications that use sound/alsa). the java packages are binary, that means that you don't compile it according to your use flags, you install the "whole package", so some libraries (like libalsasound.so) will complain if you don't have alsa support. I'm having this problem with opera and libXm but I just ignore it.
btw, is there anyway to tell revdep-rebuild to ignore a package? it's really not comfortable to run revdep-rebuild -p and then manually re-install the packages that complain (because I don't want it to re-install opera every time). Bye -- Haim
signature.asc
Description: This is a digitally signed message part
