From: Remy Blank <remy.blank_asps@pobox.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Update to glibc-2.4-r3 with gcc-3.4.6
Date: Fri, 15 Sep 2006 12:24:20 +0200 [thread overview]
Message-ID: <eedv0l$3bd$1@sea.gmane.org> (raw)
In-Reply-To: <d18977190609150248k5d00942bh87f06d549196ba89@mail.gmail.com>
David Grant wrote:
> I did and I totally screwed up my system. I managed to fix it eventually
> by booting to a live CD and untaring the quickpkg I made into the /
> directory.
Yes, I saw your posts on bug 125868 [1].
> ... and secondly, don't
> do it until you get some responses back from others who did it succesfully.
Well, I did it anyway (had a bit of time on my hands). And surprise, I
had the exact same symptoms as the bug above, i.e. a relocation error
before unmerging the previous glibc-2.3.6-r4. But everything was still
working ok.
So I did *not* panic ;-) and just emerged glibc-2.4-r3 a second time (I
had made a binary package, so this was quite fast), and this time the
previous glibc was unmerged correctly. I suppose an emerge --prune would
also have worked. Your problem was most likely due to your having
unmerged glibc-2.4, which left you with a system without glibc.
So there does seem to be a bug, albeit not really a critical one, in the
merge process. But it can be fixed easily by unmerging the *old* glibc
version.
-- Remy
[1] http://bugs.gentoo.org/show_bug.cgi?id=125868
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-15 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 7:54 [gentoo-user] Update to glibc-2.4-r3 with gcc-3.4.6 Remy Blank
2006-09-15 9:48 ` David Grant
2006-09-15 10:24 ` Remy Blank [this message]
2006-09-15 16:52 ` [gentoo-user] " David Grant
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='eedv0l$3bd$1@sea.gmane.org' \
--to=remy.blank_asps@pobox.com \
--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