From: Alex Bennee <alex@bennee.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] ldconfig breaks my system
Date: Mon, 18 Jul 2005 07:24:30 +0000 [thread overview]
Message-ID: <1121671470.21678.7.camel@malory> (raw)
In-Reply-To: <42DB0CF3.9080609@gmail.com>
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
--
Alex, homepage: http://www.bennee.com/~alex/
If you had better tools, you could more effectively demonstrate your
total incompetence.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-18 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 12:31 [gentoo-amd64] ldconfig breaks my system Alex Bennee
2005-07-15 16:13 ` Zac Medico
2005-07-17 18:14 ` Alex Bennee
2005-07-17 20:38 ` [gentoo-amd64] " Duncan
2005-07-18 1:59 ` [gentoo-amd64] " Zac Medico
2005-07-18 7:24 ` Alex Bennee [this message]
2005-07-18 7:48 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1121671470.21678.7.camel@malory \
--to=alex@bennee.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox