I decided today to update the 'world' ;) After getting the newest portage I did a 'emerge -u world' 17 of the 27 updates installed but it crashed right after the 17th. The issue is this: I had glibc2.3.2-r1. Portage unemerged glibc2.3.2-r1 to install glibc2.3.1-r4 (don't know why). Everything installed properly (for this package). Now if I enter emerge or startx or other program using glibc I get: Python2.2: /lib/libpthread.so.0 : version 'GLIBC_2.3.2' not found (required for python2.2) Is it me ? is it portage or glibc or what ? It's my first bug report so bare with me. If there's any info that would be valuable to you, just email me. I want to help the community. If it's something I've done then I think we should be aware of it because I didn't changed any settings. My installation is like new. Only emerged some apps. Thanks for your time. I hope this will help us. Greg
I was thinking about it and there's something I want to add. I started by updating portage than portage told me I needed to update some files. So I did etc-update. And one of the three files was make.globals or something and I replaced the file with the newest version. And I think that could be the reason. If it's not then I'm more lost than I thought. Hope this help.
Im going to close this bug because i think what happened was this: 1) You were using ~x86 at some point, somehow, either through your make.conf or the command line 2) You upgraded portage 3) during your etc-update you let it overwrite your make.conf thus reverting you to x86, and forcing a glibc downgrade. and to fix this issue, visit http://cvs.gentoo.org/~avenj/bins/ and grab the glibc tar and follow the instructions listed.
