I tried to emerge gtk+ 2.4.14 when it went stable in portage today, and the emerge failed with the following output: /bin/sh ../libtool --mode=link i686-pc-linux-gnu-gcc -O2 -march=pentium4 -funroll-loops -fomit-frame-pointer -pipe -Wall -o libpixbufloader-tiff.la -rpath /usr/lib/gtk-2.0/2.4.0/loaders -avoid-version -module io-tiff.lo -ltiff libgdk_pixbuf-2.0.la -lgmodule-2.0 -ldl -lgobject-2.0 -lglib-2.0 -lm grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la' is not a valid libtool archive make[4]: *** [libpixbufloader-tiff.la] Error 1 make[4]: Leaving directory `/var/tmp/portage/gtk+-2.4.14/work/gtk+-2.4.14/gdk-pixbuf' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/gtk+-2.4.14/work/gtk+-2.4.14/gdk-pixbuf' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/tmp/portage/gtk+-2.4.14/work/gtk+-2.4.14/gdk-pixbuf' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gtk+-2.4.14/work/gtk+-2.4.14' make: *** [all] Error 2 I recently upgraded from gcc 3.3.4 to gcc 3.3.5, but I don't think that would have anything to do with it. It appears that I don't have libstdc++ installed, (and portage verified this to be correct because the only version of libstdc++ is masked). Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge -u gtk+ 3. Actual Results: Ebuild fails as noted above. Expected Results: Ebuild should have succeeded. Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r4 i686) ================================================================= System uname: 2.6.10-gentoo-r4 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHzGentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1,sys-kernel/linux26-headers-2.6.8.1-r2 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -funroll-loops -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -funroll-loops -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://www.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="X alsa apache2 apm avi berkdb bitmap-fonts crypt cups encode esd f77 fam flac foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 guile imagemagick imlib ipv6 jpeg junit ldap libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls nvidia odbc oggvorbis opengl oss pam pda pdflib perl png python quicktime readline ruby ruby18 sdl slang spell sqlite ssl svga tcltk tcpd tetex tiff truetype x86 xml xml2 xmms xv zlib"
remerging tiff made this error go away for me.
From the mail list - it worked for me, too. Do fix_libtools.sh to get help. Date: Wed, 12 Jan 2005 22:09:36 -0600 From: Gabriel M. Beddingfield <gabriel@teuton.org> Reply-To: gentoo-user@lists.gentoo.org To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: gcc-upgrade -> link faild (wrong libstdc++.la) Sascha Lucas wrote: > Hi Boyd, > >> $ su - >> # fix_libtool_files.sh 3.3.4 > > thanks a lot. now it works fine. > I had the exact same problem. This fixed it for me also.
*** This bug has been marked as a duplicate of 73435 ***
*** Bug 77789 has been marked as a duplicate of this bug. ***
