Upgrading gcc from 3.2.3 to 3.3.2 broke python, because python is compiled against gcc's C++ library. The gcc upgrade removes the gcc-3.2.3 libraries, and installs the gcc 3.3.2 libraries. Python can't run until ld.so.conf is updated to point to the new gcc libraries. This is fixed by env-update (and the ldconfig that occurs as part of that). Only problem is ... env-update is written in python and so couldn't run. Doh. It's fixable by hand - but it shouldn't have broken in the first place. env-update really needs to be written as a shell script - one that relies on a static shell, so that it becomes immune to this kind of stupid bug. Best regards, Stu Reproducible: Always Steps to Reproduce: 1. 2. 3.
As env-update appears to be part of Portage, and is definitely the problem here, I've copied the Portage team in on this.
Err... I went through this upgade. I suspect this was fixed, and the bug got ignored. Slapping it shut, gcc-porters, reopen if it still exists (cc dev-portage if we have to do anything, although I doubt it).
