public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Bennee <alex@bennee.com>
To: Gentoo AMD64 <gentoo-amd64@lists.gentoo.org>,
	Gentoo Users <gentoo-user@lists.gentoo.org>
Subject: [gentoo-amd64] ldconfig breaks my system
Date: Fri, 15 Jul 2005 13:31:53 +0100	[thread overview]
Message-ID: <1121430713.8121.9.camel@malory> (raw)

Hi,

Applogies for the cross-post. I'm unsure if this is and amd64 specific
problem or a more general b0rkage.

I've posted about my failing glibc emerges before:

http://thread.gmane.org/gmane.linux.gentoo.user/114627

I think I've narrowed it down to ldconfig running during the emerge. In
fact at the moment any time I run ldconfig it breaks the system so that
I cannot spawn any new shells (they segfault straight away). I can
restore my system by untaring a rescue glibc binary.

Can anyone give me any hints on how to diagnose the problem with
ldconfig and why things stop working when its done?

I'm currently building a parallel world on a second partition (in a
chrooted environment) to see if there are any differences between the
two setups (i.e a subtle breakage occured and was never picked up).

--
Alex, homepage: http://www.bennee.com/~alex/
It destroys one's nerves to be amiable every day to the same human
being. -- Benjamin Disraeli

-- 
gentoo-amd64@gentoo.org mailing list



             reply	other threads:[~2005-07-15 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-15 12:31 Alex Bennee [this message]
2005-07-15 16:13 ` [gentoo-amd64] ldconfig breaks my system 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
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=1121430713.8121.9.camel@malory \
    --to=alex@bennee.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    --cc=gentoo-user@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