after gcc-3.4.3 emerge, emerge itself won't work anymore

[eniacght]

Hi,

i've just emerged gcc-3.4.3. Now my hole system seems to be trouble. I cannot emerge anything, everytime i get
/usr/bin/python: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

I tried with the livecd and chroot into my system. But still the same problem. Any ideas, how i can get my system to work again?

Thanks,
Henning

[bkunlimited]

try

[eniacght]

I just run the command and says it fixes and fixes ... mostly kde ...

After that emerge still won't work.

I've also tried gcc-config x86_64-pc-linux-gnu-3.4.3 which tells me, that it can't locate that file in /etc/env.d/gcc/
In that folder are just all files for 3.4.2 and for 3.4.4. Now i'm wondering, as i never emerged a 3.4.4. I checked /var/tmp/portage, which says, i've emerged a gcc-3.4.3-20050110-r2
I think emerge messed something nasty up.

[eniacght]

Ok, now it starts to be quiet strange.

I ran find to search for libstdc++.so.6 and it was found under /usr/lib/gcc-lib/x86_64-linux-gnu-3.4.2 and 3.4.4, so i tried to switch to 3.4.4 with gcc-config. That command tells me, it can't find libstdc++.so.6

Now, i'm stuck. The program that is supposed to fix the problem, is also hit by the problem ...

[AlfaGTV]

I have the same problem, just did an emerge -uDv world and my system is borked.
/usr/bin/python: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

edit:

I can't select a gcc version anymore

root@DUAL-ATHLON3 mathias # gcc-config -l
[1] i686-pc-linux-gnu-3.3.4
[2] i686-pc-linux-gnu-3.4.4
[3] i686-pc-linux-gnu-3.4.4-hardened
[4] i686-pc-linux-gnu-3.4.4-hardenednopie
[5] i686-pc-linux-gnu-3.4.4-hardenednopiessp
[6] i686-pc-linux-gnu-3.4.4-hardenednossp

root@DUAL-ATHLON3 mathias # gcc-config i686-pc-linux-gnu-3.4.4
* Switching to i686-pc-linux-gnu-3.4.4 compiler...
/usr/bin/python: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
* /usr/bin/gcc-config: Could not get portage CHOST!
/usr/bin/gcc-config: line 1: env: command not found
* /usr/bin/gcc-config: Could not get portage CHOST!
/usr/bin/python: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
* /usr/bin/gcc-config: Could not get portage CHOST!
/usr/bin/python: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
* /usr/bin/gcc-config: Could not get portage CHOST!
/usr/bin/python: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
* /usr/bin/gcc-config: Could not get portage CHOST! [ ok ]
_________________
Cuore Sportivo

[RaZoR1394]

Same problem here too with a ~x86 installation after updating world. In my case I upgraded too GCC 3.4.4 from 3.4.3. I have recently upgraded my ~amd64 to GCC 3.4.4 without any problems.

I would be very grateful if anyone finds a solution. I've tried fix_libtool_files.sh 3.4.4. The env-update command won't work and I´ve tried "source /etc/profile".

[BeesTea]

Here's a quick fix.

# ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6 /lib/libstdc++.so.6

# env-update

# gcc-config i686-pc-linux-gnu-3.4.4

# fix_libtool_files.sh 3.4.3

# source /etc/profile

# rm /lib/libstdc++.so.6

#EDIT change 3.4.4 to 3.4.3 and 3.4.3 to 3.whatever.you.had.before if you ran into the problem moving to 3.4.3 and not 3.4.4

[mac_bain]

Hi,
this solved the problem for me:

1. ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6 /usr/lib/libstdc++.so.6
2. gcc-config 1
3. fix_libtool_files.sh 3.4.4
4. fix_libtool_files.sh 3.4.3

Now you are able to switch to another gcc-config again.
See gcc-config -l.
Hope that helps.
chris

BeesTea solution wasn't online when I added mine.

[AlfaGTV]

[RaZoR1394]

BeesTea Thanks a lot. Your tip fixed it.

edit:

It should be 3.4.3-20050110 not 3.4.3 when doing fix_libtool...

[mac_bain]

Got a new problem here.

Wenn I use fix_libtool_files.sh 3.4.3 it seems like everything went fine.
The output shows which files have been fixed.
But when I use fix_libtool_files.sh 3.4.3 again there are the same fixing messages again.

When I try to emerge Kile I get this:
...
libtool: link: cannot find the library `//usr/lib/gcc/i686-pc-linux-gnu/3.4.3-20050110/libstdc++.la'
...
Seems like fix_libtool_files.sh did'nt get it's job done.
Does anyone know what to do?

[mac_bain]

Not my my day...
Must be fix_libtool_files.sh 3.4.3-20050110 not 3.4.3
Everything works now.
Sorry ...

[cold]

I have the same problem But on AMD64

I chanched ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6 /lib/libstdc++.so.6
in

ln -s /usr/lib64/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6 /lib/libstdc++.so.6
But I still can't run env-update
I also tried ln -sf /usr/lib64/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6 /lib64/libstdc++.so.6
but with the same result


Edit:
I was sleping it had to be ln -s /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/libstdc++.so.6 /lib64/libstdc++.so.6

[gigs_42]

Here's another one of the same problem...upgrading world borked everything. However, in my case, I can't really run anything that seemed to work for everyone else on this post. fix_libtool_files.sh failed, as does env-update after linking as beestea suggested. I always get that same message:

[sixofseven]

[quote="mac_bain"]Hi,
this solved the problem for me:

1. ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so.6 /usr/lib/libstdc++.so.6
2. gcc-config 1
3. fix_libtool_files.sh 3.4.4
4. fix_libtool_files.sh 3.4.3-20050110

Now you are able to switch to another gcc-config again.
See gcc-config -l.
[/quote]

Thank you ... This saved my day!

[John-Boy]

BeasTea - thanks, that helped me out as well.

I was about to start rebuilding my toolchain when I got hit with this, should I wait for Portage to fix whatever causes this, or continue - and apply the fix at the end of each emerge of gcc ? I'm assuming that I'd need to ..
_________________
Like the Roman, I seem to see "the River Tiber foaming with much blood"

[thomasando]

[hoschi]

[chratnox]

[menschmeier]

Hi,

I have the same problem but I even can not do

[menschmeier]

Ok,

I ignored the errors and continue, now gcc seems to work, but gcc-config always complains when I try to set an other gcc version ...

menschmeier
_________________
Please notice the back of this message.

[synapseattack]

I have a simular problem... I did a emerge --update world this morning and now i am having all kinds of problems.

AMD64 3.4.4 # emerge sync
/usr/bin/python: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

ls -l /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/libstdc++.so.6.0.3
-rwxr-xr-x 1 root root 0 Jun 3 07:42 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/libstdc++.so.6.0.3

ls -l /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/libstdc++.so.6
lrwxrwxrwx 1 root root 18 Jun 3 05:36 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/libstdc++.so.6 -> libstdc++.so.6.0.3

ls -l /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/libstdc++.so
lrwxrwxrwx 1 root root 18 Jun 3 05:36 libstdc++.so -> libstdc++.so.6.0.3

The file is basically empty so the two pointers to the file are pointing, for all intents and purposes, to nothing. I am guessing I need to find a way to either download them from the net or something. But I don't want to do the wrong thing and screw the system up more. I searched the web and found references 3.4.3 problems that are simular but not exactly the same thing. Has anyone run accross this before. Any hints on what to do next?
_________________
~Syn

[RaZoR1394]

As I said before emerge started working after using BeesTea's fix but it broke just when make'ing the first package (kdelibs) throwing me the "libstdc++.la - Not a valid libtool archive" error. I followed the FAQ for that error and none of the recommended fixes worked so I had to make a 3.4.3 symlink to the the 3.4.4 dir under /usr/lib/gcc/i686-pc-linux-gnu which wasn't recommended.

Here's the FAQ I followed.

[synapseattack]

[red-wolf76]