When installing glibc-2.3.5 there comes a time when "emerge" says: >>> Regenerating /etc/ld.so.cache... >>> sys-libs/glibc-2.3.5-r2 merged. [glibc-2.3.5-r2] bash: relocation error: /lib/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference
# emerge info /usr/bin/python: relocation error: /lib/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference
post your make.conf as an attachment
After untar'ing an old glibc-2.3.3 the system came up again. However I cannot do an emerge -a -v -k /remote/usr/portage/packages/All/glibc-2.3.3.tar.bz2 The emerge mechanism deletes more files than it has license to do. However emerging by path has an appropriate warning.
k
Created attachment 77176 [details] chrooted Gentoo in the process of being updated, glibc and all The make.conf really does not matter here, but thanks for the interest.
Error: The /usr/crt1.o did not match the glibc package. Reason unknown. The reason why python did not run properly may be related to to wrong crt1.o or libpthread.o and so on. Solved by untar-ing another glibc. Sorry for this false bugreport. Regards/Donald Axel