| 1 |
On Friday 12 February 2010 21:55:29 Alan Mackenzie wrote: |
| 2 |
> Hi, Gentoo! |
| 3 |
> |
| 4 |
> As reported in other threads, my new PC had a broken RAM stick in it. |
| 5 |
> As a result, an unknown proportion of installed binaries are flaky. One |
| 6 |
> non-functioning binary is probably GCC. |
| 7 |
> |
| 8 |
> What I'd like to do is reinstall every binary, yet without erasing any |
| 9 |
> configuration info, whose creation was so arduous. |
| 10 |
> |
| 11 |
> Where does portage keep it's list of installed packages? What do I have |
| 12 |
> to do to persuade portage it has _no_ installed packages before doing |
| 13 |
> 'rm -rf *' in /bin, /sbin, /usr/bin, /usr/sbin? |
| 14 |
> |
| 15 |
> Has anybody any other tips to offer me for this operation? |
| 16 |
|
| 17 |
First get a working compiler installed. There are many ways, here's what I |
| 18 |
think is the easiest: |
| 19 |
|
| 20 |
Boot into a Gentoo LiveCD, chroot into your install, and emerge -k the gcc |
| 21 |
tarball on the CD. |
| 22 |
|
| 23 |
Reboot into the actual install, synce the portage tree and |
| 24 |
|
| 25 |
emerge -e world |
| 26 |
|
| 27 |
That will rebuild everything, including gcc. |
| 28 |
|
| 29 |
The paranoid might want to emerge gcc itself on it's own first so that |
| 30 |
rebuilding world is done with the same gcc version as what it will become (gcc |
| 31 |
is not built first when you rebuild world, all sort of toolchain tools and |
| 32 |
parsers are earlier in the list). Personally, I don't do that - there is an |
| 33 |
actual chance that using an old compiler to build a new compiler may lead to |
| 34 |
incompatibility issues, but the risk is extremely small and rare, and it's |
| 35 |
never bitten me. |
| 36 |
|
| 37 |
-- |
| 38 |
alan dot mckinnon at gmail dot com |
Archives