| 1 |
Thanks for the advice folks. |
| 2 |
As it turned out I had enough of the lib left to keep some of the |
| 3 |
system running and I managed to copy over sufficient to get a working |
| 4 |
connection going then after much more thrashing of the head on desk it |
| 5 |
turned out that my backup was sufficient to get portage working pretty |
| 6 |
well phew |
| 7 |
I am now working on the --emptytree to restore everything properly. |
| 8 |
|
| 9 |
stu |
| 10 |
|
| 11 |
ps. tip of the day when spring cleaning your system watch out for |
| 12 |
those little typos that can ruin your summer :) |
| 13 |
pps. Just for fun it went something like this, |
| 14 |
"rm -rf /usr/lib/libcrco.so /usr/lib/ /usr/lib/bochs /usr/lib/libcroco.co.0" |
| 15 |
|
| 16 |
|
| 17 |
|
| 18 |
|
| 19 |
On 19/10/06, Nico Schümann <nico.schuemann@××××××××××.com> wrote: |
| 20 |
> 2006/10/19, Mark <znxster@×××××.com>: |
| 21 |
> > If not then you will need to acquire a binary gcc/etc to work around |
| 22 |
> > it. Then rebuild. |
| 23 |
> > |
| 24 |
> > emerge -e world |
| 25 |
> |
| 26 |
> I think, after having set up the tool chain, you'd do a |
| 27 |
> emerge -e system and then |
| 28 |
> emerge -e world, |
| 29 |
> because the system packages aren't considered by the world file, are they? |
| 30 |
> |
| 31 |
> Anyway, good luck. |
| 32 |
> -- |
| 33 |
> gentoo-user@g.o mailing list |
| 34 |
> |
| 35 |
> |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
"There are 10 types of people in this world: those who understand |
| 40 |
binary, those who don't" |
| 41 |
|
| 42 |
--Unknown |
| 43 |
|
| 44 |
-- |
| 45 |
gentoo-user@g.o mailing list |
Archives