public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How should I clean up my broken system?
Date: Sat, 13 Feb 2010 09:27:15 +0200	[thread overview]
Message-ID: <201002130927.15466.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20100212195529.GD1560@muc.de>

On Friday 12 February 2010 21:55:29 Alan Mackenzie wrote:
> Hi, Gentoo!
> 
> As reported in other threads, my new PC had a broken RAM stick in it.
> As a result, an unknown proportion of installed binaries are flaky.  One
> non-functioning binary is probably GCC.
> 
> What I'd like to do is reinstall every binary, yet without erasing any
> configuration info, whose creation was so arduous.
> 
> Where does portage keep it's list of installed packages?  What do I have
> to do to persuade portage it has _no_ installed packages before doing
> 'rm -rf *' in /bin, /sbin, /usr/bin, /usr/sbin?
> 
> Has anybody any other tips to offer me for this operation?

First get a working compiler installed. There are many ways, here's what I 
think is the easiest:

Boot into a Gentoo LiveCD, chroot into your install, and emerge -k the gcc 
tarball on the CD.

Reboot into the actual install, synce the portage tree and 

emerge -e world

That will rebuild everything, including gcc. 

The paranoid might want to emerge gcc itself on it's own first so that 
rebuilding world is done with the same gcc version as what it will become (gcc 
is not built first when you rebuild world, all sort of toolchain tools and 
parsers are earlier in the list). Personally, I don't do that - there is an 
actual chance that using an old compiler to build a new compiler may lead to 
incompatibility issues, but the risk is extremely small and rare, and it's 
never bitten me.

-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2010-02-13  7:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 19:55 [gentoo-user] How should I clean up my broken system? Alan Mackenzie
2010-02-12 19:55 ` Volker Armin Hemmann
2010-02-12 21:21   ` Kyle Bader
2010-02-12 22:52     ` Neil Bothwick
2010-02-13  7:28       ` Alan McKinnon
2010-02-13 20:43         ` Neil Bothwick
2010-02-14  6:01           ` Alan McKinnon
2010-02-14  9:34             ` Neil Bothwick
2010-02-14 11:03               ` Volker Armin Hemmann
2010-02-14 11:32                 ` Neil Bothwick
2010-02-20 12:08                   ` Mick
2010-02-20 12:20                     ` Volker Armin Hemmann
2010-02-21  0:22                     ` Neil Bothwick
2010-02-21  3:12                     ` Iain Buchanan
2010-02-22 11:29                       ` daid kahl
2010-02-22 13:56                         ` Volker Armin Hemmann
2010-02-22 17:06                           ` [gentoo-user] " Harry Putnam
2010-02-26  7:29                             ` daid kahl
2010-02-26 18:20                   ` [gentoo-user] " Peter Humphrey
2010-02-26 18:47                     ` Alex Schuster
2010-02-27  1:02                       ` Peter Humphrey
2010-02-12 23:46 ` William Kenworthy
2010-02-13  7:27 ` Alan McKinnon [this message]
2010-02-13 17:51   ` Alan Mackenzie
2010-02-13 18:50     ` Stroller
2010-02-14  6:00     ` Alan McKinnon

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=201002130927.15466.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.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