| 1 |
On Saturday 13 February 2010 19:51:05 Alan Mackenzie wrote: |
| 2 |
> Thanks! In the end, I just used the gcc I had on the system anyway; it |
| 3 |
> wasn't broken. I first did 'emerge -e gcc', which took an hour, then did |
| 4 |
> 'emerge -e world', which took ~2 hours 30 mins. |
| 5 |
> |
| 6 |
> I was being a bit paranoid. The reason I "gave up" on the installation |
| 7 |
> CD was I failed to find out how to start my LVM2 voluble logics, or |
| 8 |
> whatever they're called. |
| 9 |
|
| 10 |
Oh yes, I forgot about that. I have old LiveCDs around too that don't support |
| 11 |
LVM. It can get bloody annoying when you forget and use it anyway. These days |
| 12 |
I use RIPLinux on a small spare USB stick as my rescue system |
| 13 |
|
| 14 |
|
| 15 |
> I'm now back on track, setting up my PC. Thanks! |
| 16 |
> |
| 17 |
> > The paranoid might want to emerge gcc itself on it's own first so that |
| 18 |
> > rebuilding world is done with the same gcc version as what it will |
| 19 |
> > become (gcc is not built first when you rebuild world, all sort of |
| 20 |
> > toolchain tools and parsers are earlier in the list). Personally, I |
| 21 |
> > don't do that - there is an actual chance that using an old compiler to |
| 22 |
> > build a new compiler may lead to incompatibility issues, but the risk |
| 23 |
> > is extremely small and rare, and it's never bitten me. |
| 24 |
> |
| 25 |
> There was that apocryphal tale of the origianl Unix hacker who hardwired |
| 26 |
> a backdoor login into the system, and hacked cc to keep inserting the |
| 27 |
> backdoor each time the system was built, and to keep this hack in cc each |
| 28 |
> time cc was compiled. Whew! |
| 29 |
|
| 30 |
That's not a myth either :-) |
| 31 |
|
| 32 |
There was a story on /. about that very thing just the other day! |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
alan dot mckinnon at gmail dot com |
Archives