gcc-3.3.5 --> gcc-4.1.2 problem

Message

lukasfischer · Post by **lukasfischer** » Fri Mar 02, 2007 8:51 pm

during emerge of gcc-4.1.2 emerging glibc failed because of too old gcc.
i was so stupid to switch to gcc-4 without working glibc and cannot switch back now:

gcc-config -f 1
* Python seems to be broken, attempting to locate CHOST ourselves ...
* Switching cross-compiler to i386-pc-linux-gnu-3.3.5-20050130 ...
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

* env-update failed to work properly; making sure ld.so.conf paths
* are setup properly. Please rerun gcc-config with the -f option.
[ ok ]

* If you intend to use the gcc from the new profile in an already
* running shell, please remember to do:

* # source /etc/profile

is there a way to go back to the old gcc? do i really have to update gcc in two steps!?!?
thanks

lukasfischer · Post by **lukasfischer** » Fri Mar 02, 2007 8:57 pm

just read the small "Important:" sign in the END of the gcc upgrade guide.
too late now. how can i get a working toolchain back?

drwook · Post by **drwook** » Fri Mar 02, 2007 9:07 pm

lukasfischer wrote:just read the small "Important:" sign in the END of the gcc upgrade guide.
too late now. how can i get a working toolchain back?

How's your portage holding up? Guessing you're past it, but can you attempt to re-emerge python, or emerge libstdc++-v3? If not, maybe go back to the good old days and try using ebuild directly to see if you have any more luck to get back to a working system...

lukasfischer · Post by **lukasfischer** » Fri Mar 02, 2007 9:16 pm

emerge --oneshot sys-libs/libstdc++-v3
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

drwook · Post by **drwook** » Fri Mar 02, 2007 9:18 pm

Code: Select all

~ # ebuild /usr/portage/sys-libs/libstdc++-v3/libstdc++-v3-3.3.6.ebuild compile

Any joy with that?

lukasfischer · Post by **lukasfischer** » Fri Mar 02, 2007 9:24 pm

same thing:

ebuild /usr/portage/sys-libs/libstdc++-v3/libstdc++-v3-3.3.6.ebuild compile
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

shouldn't i switch back to gcc-3.3.5 first?

lukasfischer · Post by **lukasfischer** » Fri Mar 02, 2007 9:47 pm

i'll go get drunk. see you tomorrow. thanks for help.

lukasfischer · Post by **lukasfischer** » Sat Mar 03, 2007 4:27 am

ok. done. i'm drunk.
tomorrow is emerge system && emerge world day.

davidgurvich · Post by **davidgurvich** » Sat Mar 03, 2007 5:18 am

Did you try fix_libtool_files.sh ?

Code: Select all

fix_libtool_files.sh previous_gcc_version
revdep-rebuild

lukasfischer · Post by **lukasfischer** » Sat Mar 03, 2007 2:43 pm

Hmmm. didn't work either...

fix_libtool_files.sh i386-pc-linux-gnu-3.3.5-20050130
* Scanning libtool files for hardcoded gcc library paths...
* [1/10] Scanning /lib ...
* [2/10] Scanning /usr/lib ...
* [3/10] Scanning //usr//lib/opengl/xorg-x11/lib ...
* [4/10] Scanning /opt/blackdown-jdk-1.4.2.03/jre/lib/i386 ...
* [5/10] Scanning /usr/games/lib ...
* [6/10] Scanning /usr/i386-pc-linux-gnu/lib ...
* [7/10] Scanning /usr/kde/3.4/lib ...
* [8/10] Scanning /usr/kde/3.5/lib ...
* [9/10] Scanning /usr/local/lib ...
* [10/10] Scanning /usr/qt/3/lib ...
asldk ~ # revdep-rebuild
Configuring search environment for revdep-rebuild
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

Checking reverse dependencies...

Packages containing binaries and libraries broken by a package update
will be emerged.

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...
done.
(/root/.revdep-rebuild.3_rebuild)

Assigning files to ebuilds... Nothing to rebuild

Evaluating package order... done.
(/root/.revdep-rebuild.5_order)

Dynamic linking on your system is consistent... All done.
asgh ~ # gcc-config 1
* Python seems to be broken, attempting to locate CHOST ourselves ...
* Switching cross-compiler to i386-pc-linux-gnu-3.3.5-20050130 ...
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

* env-update failed to work properly; making sure ld.so.conf paths
* are setup properly. Please rerun gcc-config with the -f option.
[ ok ]

* If you intend to use the gcc from the new profile in an already
* running shell, please remember to do:

* # source /etc/profile

Assgier · Post by **Assgier** » Sat Mar 03, 2007 2:59 pm

The easyest solution would be to post your /proc/cpuinfo.

Someone using the same arch could perhaps post a binary version of libstdc++.so.5 for you to use, it would be a lot faster then emerging system/world

lukasfischer · Post by **lukasfischer** » Sat Mar 03, 2007 5:09 pm

thanks for help, but i'm reinstalling the system. not the first problem and probably not the last one i ran into trying to update cinelerra-cvs on a 1.5 year old system. i like linux, but updates are a pain in the ***.

hielvc · Post by **hielvc** » Sun Mar 04, 2007 3:20 am

When you re-install make sure you grab a i586 or i686 stage3. You cant install the latest glibc, nptl, on a box that claims to be a i386 and thats what eill happen if you use i386 stage3.