| 1 |
--- Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
|
| 3 |
> On Tuesday 29 January 2008, Mick wrote: |
| 4 |
> |
| 5 |
> > Retrace your steps and follow the guide on this |
| 6 |
> one. I'm sure that |
| 7 |
> > you can recover if you ended up with no gcc, but |
| 8 |
> don't know off hand |
| 9 |
> > what it takes to do it. (I am sure that the |
| 10 |
> forums are full of |
| 11 |
> > suggestions for this problem). |
| 12 |
> |
| 13 |
> Easy. Grab any old gcc tarball from an install cd, |
| 14 |
> use emerge to unpack |
| 15 |
> this as a binpkg. This gives you a probably less |
| 16 |
> than optimum but |
| 17 |
> working gcc, which can be used to build the desired |
| 18 |
> gcc. Then unmerge |
| 19 |
> the unpacked one. |
| 20 |
> |
| 21 |
> |
| 22 |
|
| 23 |
It wasn't gcc. See Volker's reply to "leapfrogging versions" |
| 24 |
|
| 25 |
|
| 26 |
____________________________________________________________________________________ |
| 27 |
Be a better friend, newshound, and |
| 28 |
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-user@l.g.o mailing list |
Archives