1 |
Thanks. Unless anyone else has any suggestions I will try it. |
2 |
|
3 |
Can anyone else confirm this is the way to go before I try? |
4 |
|
5 |
Regards, |
6 |
|
7 |
Rupert |
8 |
|
9 |
> -----Original Message----- |
10 |
> From: Dave Nebinger [mailto:dnebinger@××××.com] |
11 |
> Sent: 21 September 2005 20:12 |
12 |
> To: gentoo-user@l.g.o |
13 |
> Subject: RE: [gentoo-user] System update problems |
14 |
> |
15 |
> > Any help appreciated. |
16 |
> > |
17 |
> > /usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible |
18 |
> /usr/lib/gcc/x86_64-pc-linux- |
19 |
> > gnu/../../libc.so when searching for -lc |
20 |
> |
21 |
> Dude, I think your build chain is now in a 'hosed' state, probably as a |
22 |
> result of the migration that you were trying... |
23 |
> |
24 |
> Since gentoo is a source-based distro you're going to have to get this |
25 |
> resolved before you can move forward. |
26 |
> |
27 |
> Others might have a better suggestion, but I'd probably approach it as |
28 |
> follows: |
29 |
> |
30 |
> 1. back up the /etc directory. |
31 |
> 2. back up the /var/lib/portage directory to keep your current world file. |
32 |
> 3. follow the 2005.1 handbook to expand the initial portage base into your |
33 |
> root filesystem. |
34 |
> 4. restore the /etc and /var/lib/portage directory contents. |
35 |
> 5. emerge --sync the system |
36 |
> 6. emerge --update --deep --emptytree --newuse world |
37 |
> |
38 |
> The last step will take quite awhile to complete (depending upon what |
39 |
> you've |
40 |
> deployed already), but it should rebuild everything including your build |
41 |
> chain. |
42 |
> |
43 |
> Now, as I said I don't know if this is the best way and would recommend |
44 |
> hearing answers from others if they post any, and only look to this as a |
45 |
> *possible* solution. |
46 |
> |
47 |
> |
48 |
> |
49 |
> -- |
50 |
> gentoo-user@g.o mailing list |
51 |
|
52 |
|
53 |
|
54 |
-- |
55 |
gentoo-user@g.o mailing list |