emerging gedit I see this error (I think that the compilation works only with a i386-pc-linux-gnu ...makefile needs to be fixed) : --------- ... Merging translations into spell.gedit-plugin. /bin/sh ../../libtool --mode=link gcc -mcpu=athlon-xp -O3 -pipe -o libspell.la -rpath /usr/lib/gedit-2/plugins -module -avoid-version spell.lo gedit-spell-checker.lo gedit-spell-checker-dialog.lo gedit-spell-language-dialog.lo gedit-automatic-spell-checker.lo gedit-spell-checker-dialog-marshal.lo -laspell -lpopt grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la' is not a valid libtool archive make[4]: *** [libspell.la] Error 1 make[4]: Leaving directory `/var/tmp/portage/gedit-2.6.0/work/gedit-2.6.0/plugins/spell' make[3]: *** [all] Error 2 make[3]: Leaving directory `/var/tmp/portage/gedit-2.6.0/work/gedit-2.6.0/plugins/spell' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gedit-2.6.0/work/gedit-2.6.0/plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gedit-2.6.0/work/gedit-2.6.0' make: *** [all] Error 2 !!! ERROR: app-editors/gedit-2.6.0 failed. !!! Function gnome2_src_compile, Line 39, Exitcode 2 !!! compile failure --------- Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.50-r6 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.6) ================================================================= System uname: 2.6.6 i686 AMD Athlon(TM) MP 1900+ Gentoo Base System version 1.4.10 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon-xp -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb cdr crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde ldap libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcltk tcpd truetype x86 xml2 xmms xv zlib"
i doubt it, i think your system needs fixing.
You might try: fix_libtool_files.sh 3.3.2 Fount it here: http://forums.gentoo.org/viewtopic.php?t=141803&highlight=libstdc+la+such+file+directory
I'm getting the same thing after upgrading from gcc-3.4.0 to gcc-3.4.1. I've removed that bad paths from /etc/env.d/00basic and /etc/env.d/05gcc and re-run env-update I've also run the fix_libtool_files.sh Anyone know how to get my system compiling again? I notice that this bug has not been fixed from 3.3.something...
I have also the same problem. I updated the profile from 2004.0 2004.2 and wanted to make the usual emerge world.
This isn't a bug, its a poorly configured system. I notice the error in comment#1 shows it looking in i386-pc-linux-gnu while their chost is set to CHOST="i686-pc-linux-gnu". They probably need to run fix_libtool_files with the --oldarch option if they have changed it. Run the script with no arguments for options.
Sorry, I call it a bug, not a feature (or a poorly configured system). At least, it doesn't seem poorly configured *by the user*. This happens even when the CHOST setting was never changed since the initial Stage 1 build (in my case) so it's also not specific to a Stage 3 (see Bug # 51360). I just don't see how this one has anything to do with a user-misconfiguration issue; gedit should not be looking for i386-foo/wrong-gcc-version.
fix it i'd say...
I've have this strange behavior too. I never changed my chost or any other compile option in my make file after stage 1. Last time emerge told me, that profile 1.4 is not supported and I sould go for 2004.0 at least. I followed the instructions. I also noticed on my system, that portage always updates to the newest gcc. Now I'm running 3.4.2 !! on my system. The problem: even revdep-rebuild can't build packages as it is missing the libstdc++ library :( So how to fix this? Or how to correctly switch profiles ?
I get a very similar problem with gentoo stable on amd64. After upgrading to gcc 3.4.3, it seems that libtool still wants to use the old 3.4.2 gcc libraries when compiling gedit. I know that fix_libtool_files.sh would probably fix the problem, but it seems more like an ugly hack to me. Why would libtool still know about the old gcc version? I even reemerged libtool and then browsed the libtool script and found no mention of 3.4.2 in it (although 3.4.3 is mentionned which is good). how could this be? Here is my info: gentoobox root # gcc-config -c x86_64-pc-linux-gnu-3.4.3 gentoobox root # gcc -dumpversion 3.4.3 here is the error: /bin/sh ../../libtool --mode=link gcc -march=athlon64 -O2 -pipe -o libspell.la -rpath //usr/lib/gedit-2/plugins -module -avoid-version spell.lo gedit-spell-checker.lo gedit-spell-checker-dialog.lo gedit-spell-language-dialog.lo gedit-automatic-spell-checker.lo gedit-spell-checker-dialog-marshal.lo -laspell -lpopt grep: /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.2/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.2/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.2/libstdc++.la' is not a valid libtool archive
I encountered this problem on a brand new 2004.3 stage 3 install. I don't think this is necessarily the user's fault - might there be something borked on the liveCD too?
*** This bug has been marked as a duplicate of 73435 ***
