When I try to Emerge kdelibs, I get an error message which tells me it cannot find libmad. [cut] rm: cannot remove `': Invalid argument rm: cannot remove `': Invalid argument /bin/sh ../../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor - Wno-long-long -Wundef -Wall -pedantic -W -Wpointer-arith -Wwrite-strings -ansi - D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -DNDEBUG -DNO_DEBUG - O2 -march=pentium3 -O2 -pipe -fno-exceptions -fno-check-new - DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT -o libartskde.la.closure libartskde_la_closure.lo -L/usr/X11R6/lib - L/usr/qt/3/lib -L/usr/kde/3.1/lib -no-undefined -version-info 2:0:1 artskde.lo kioinputstream_impl.lo kplayobject.lo kplayobjectfactory.lo kartsfloatwatch.lo kartsdispatcher.lo kaudiorecordstream.lo kartsserver.lo kdatarequest_impl.lo kaudioconverter.lo kvideowidget.lo kplayobjectcreator.lo ../../kio/libkio.la - lqtmcop -lsoundserver_idl libtool: link: cannot find the library `/var/tmp/portage/libmad-0.15.0b- r1/image//usr/lib/libmad.la' make[3]: *** [libartskde.la.closure] Error 1 make[3]: Leaving directory `/var/tmp/portage/kdelibs-3.1.4/work/kdelibs- 3.1.4/arts/kde' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/kdelibs-3.1.4/work/kdelibs- 3.1.4/arts' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/kdelibs-3.1.4/work/kdelibs-3.1.4' make: *** [all] Error 2 !!! ERROR: kde-base/kdelibs-3.1.4 failed. !!! Function kde_src_compile, Line 137, Exitcode 2 !!! died running emake, kde_src_compile:make Reproducible: Always Steps to Reproduce: 1. Start with a nice, new, fresh system. 2. emerge kdelibs Actual Results: kdelibs ebuild failed with error message detailed above. Expected Results: Linked libmad and continued with emerge. * media-libs/libmad Latest version available: 0.15.0b-r1 Latest version installed: 0.15.0b-r1 Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.20-gentoo- r8) ================================================================= System uname: 2.4.20-gentoo-r8 i686 Intel(R) Pentium(R) 4 CPU 2.26GHz Gentoo Base System version 1.4.3.10 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O2 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share /config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=pentium3 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif gpm imlib jpeg libg++ libwww mad mikmod motif mpeg ncurses nls pdflib png quicktime sdl spell svga truetype xml2 xmms xv zlib gdbm berkdb slang readline tcpd pam ssl perl python opengl X -gnome -gtk usb scanner ppds apache2 mysql gd php kde qt -arts oggvorbis" There is a workaround in the detailed forum URL that I plugged in above, but it is relatively messy and untested.
Can you eyeball /usr/lib/libmad.la and see if it has a reference to that file?
root@leagueworks lib # pwd /usr/lib root@leagueworks lib # ls -l libmad.la -rwxr-xr-x 1 root root 693 Nov 27 09:05 libmad.la Sorry is that hat you mean? :) *relative linux newbie...*
Created attachment 21333 [details] Just libmad.la as a text file
The upload was what I meant, thank you. Unfortunately it doesn't give any clue as to why this is going wrong. I'll see if I can duplicate the problem.
Just to let you know, the workaround: ln -s / /var/tmp/portage/libmad-0.15.0b-r1/image allowed me to emerge kdelibs successfully as per the forum post... Hopefully that will give you some idea as to what might be going wrong...
You should *not* make that link. Doing so is very bad =p Anyway, my friend who also had this problem had a slightly different situation, as seen from this grep: luke-jr@chewy lib $ grep image libmad* libmad.la:libdir='/var/tmp/portage/libmad-0.15.0b-r1/image//usr/lib' Changing this path to what it should be should fix the problem.
I have same problem, however, in libmad.la, line 32: libdir='/usr/lib' .
Had this same problem with someone in #gentoo, got them to do luke-jr's grep and got the same result he did. Funnily enough, I then checked it on my system and found I had it too. However, My arts-1.2.0_rc1 compiled just fine (it's a masked version). I'm not sure why. I have USE="mad".
Had one person having this problem with /usr/lib/libfreetype.la
this stuff has all been fixed, but you may need to perform some manual cleanup as described in the forums. it's a bug elsewhere
