Sorry, thats not applicable in this case (its not a portage problem) Just about every link to libgcc_s.so.1 is via gcc-3.1.1 and therefore requires a matching 3.1.1 libstc++.so.5 (in pythons case). Because the system has been built with split versions, its impossible (so far) to work out links that allow things to work, but compile against the latest versions which will correct the problem. There appears to be a couple hundred or so libs/binaries using 3.1.1, but only a small, but critical number appear to have this split version problem. I have no idea what is the original cause, but this system dates from the first gentoo gcc 3.0 release - something went wrong in the early days I guess.
BillK On Sun, 2004-02-08 at 21:50, Peter Ruskin wrote: > > > Try 'env-update && ldconfig'. But remove your symlinks before doing > > > that. > > > > /usr/portage/sys-apps/portage/files/README.RESCUE might be worth a try. > > Peter -- [EMAIL PROTECTED] mailing list
