Alex Bennee wrote:
On Sun, 2005-07-17 at 18:59 -0700, Zac Medico wrote:
Alex Bennee wrote:
Yes that one. I've been unable to succesfully upgrade to 2.3.5 without
hitting the failure. However I left my system building a fresh partition
from scratch over the weekend - it managed to upgrade to 2.3.5 without a
problem.
Something has obviously broken on my main partition that is preventing
the update. Perhaps the difference in ld.so.conf explain things?
So, your system is still broken? You can use quickpkg to make a binary package
from the glibc that you built on the fresh partition. Try to install that
binary package.
If that doesn't work then you can do it by brute force: untar the binary
package directly
onto your broken system and run ldconfig.
I wasn't able to install the binary package properly (as ldconfig is
called during the emerge process). However as I was stracing the
ldconfig output to compare with the working setup I realised I wasn't
logging stderr so hit Ctrl-C and restarted ldconfig.
This seems to of "unstuck" the ldconfig failure and I have been able to
run ldconfig without breaking things since. I've done a proper src
emerge of glibc on a chrooted in my original partiton and everything
seems to be working ok now.
The config has been updated during the env-update so I wonder if it was
a subtle breakage in the config that was causing the failure?
malory etc # diff -ub ld.so.conf ldconfig.backup/ld.so.conf
--- ld.so.conf 2005-07-17 22:41:47.000000000 +0100
+++ ldconfig.backup/ld.so.conf 2005-06-19 23:31:13.000000000 +0100
@@ -10,9 +10,7 @@
/usr/lib32
/usr/local/lib32
/usr/x86_64-pc-linux-gnu/lib
-/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3
-/usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.4.2
-/usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.4.2/32
+/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/.
/usr/lib/MozillaFirefox
/usr/lib/mozilla
/usr/lib
I don't know. See if you can break it again, then we'll know for sure 8-).
Zac
--
[email protected] mailing list
