stage3, ARCH="~x86", gcc-3.3.2 chroot enviroment, emerge system -u. THe next package to emerge after gcc-3.3.2 was linux-headers which borked after "make oldconfig" as something was needed from 3.2.3./libstdc++.so.5. "emerge" was broken because python was hunting for guess what;^) The problem is that libstdc is now in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2 after emerge gcc-3.3.2 and of cource python and others are looking for ...gnu/3.2.3. My hack "ln -s /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2 /usr/lib/gcc-lib/i686-pc-linu-gnu/3.2.3" This is probably a dup of bug 25164. Reproducible: Always Steps to Reproduce: 1. emerge "ACCEP..."="~x86" gcc 2. 3. Actual Results: Alot of things were broken includeing python ergo portage. Expected Results: Updated libraries ? CFLAGS="-Os march=i686 -funroll-loops -pipe"
you probably have a bunch of broken .la files
This is all binary packages you used?
1. Started a new install. I used a stage3-i686-200309??.tar.bz2. 2.mounted everything, chrooted, etc, synced, edited make conf to ACCEPT_KEYWORDS-"~X86" and CFLAGS=" -march=i686 -Os -funroll-loops -pipe" 3.Then "emerge system -u". 10 compiles, packages, later emerged gcc-3.3.2-r2?. The next package to build was linux-headers-2.4.21 and it failed when it started to install them. I then tried "emerge system -up" and it crashed with a message that python couldnt find something from libstdc++.so.5 which was also mentioned in the failed install of linux-headers. So no this was a stage3 build which I was updateing to ~x86 so that my compileriers would match and I could use my athlon-xp 2000 to help this 466 celery, I can remove my symlink and give you the exact failures.
You did not see anything like: -- * Scannig libtool files for hardcoded gcc library paths... * Scanning /lib... ... -- after gcc merge ?
Well the problem is gone. Thursday night I upgraded to gcc-3.3.2-r6 form 3.3.2-r5. I removed the link this morning and ran "emerge -s sources" and nocomplaints. I really cant recall * Scannig libtool files for hardcoded gcc library paths... * Scanning /lib... and as I havent install a logger yet, I cant look in /var/log/portage either or I did but there isnt even a ../log/portage directory. Well I guess that closes this bug. Now to file one on "mirrorselect" which borked make.conf and my screen and continues to if I cat /etc/mak.. or less it. it.
K, some ld.so weirdness maybe?
This need some more discussion
*** This bug has been marked as a duplicate of 40694 ***
