| 1 |
Neil Bothwick <neil@××××××××××.uk> writes: |
| 2 |
|
| 3 |
> On Thu, 4 Feb 2010 22:13:20 +0800, Leon Feng wrote: |
| 4 |
> |
| 5 |
>> I have seen this for weeks, but since I upgrade to portage-2.2* at the |
| 6 |
>> same time, do not know whether it is related. My revdep-rebuild out is |
| 7 |
>> listed below, anyone has a solution? |
| 8 |
> |
| 9 |
> Are you also running the testing gentoolkit? Otherwise you're trying to |
| 10 |
> use the old revdep-rebuild wit the new portage, which may have |
| 11 |
> unexpected consequences. |
| 12 |
> |
| 13 |
> Have you run lafilefixer --justfixit? This should always be the first |
| 14 |
> step when revdep-rebuild reports problems. |
| 15 |
|
| 16 |
You were speaking to Leon no me (The OP), but since my output was |
| 17 |
identical, I'll report too: |
| 18 |
|
| 19 |
I'm running ~x86 on everything and latest version of gentoolkit (I |
| 20 |
don't have gentoolkit-dev installed) |
| 21 |
|
| 22 |
I've emerged lafilefixer (thanks Steve) and ran |
| 23 |
lafilefixer --justfixit |
| 24 |
|
| 25 |
Then ran revdep-rebuild again.... it still finds broken binutils so |
| 26 |
I'm letting it `oneshot' the emerge. |
| 27 |
|
| 28 |
Was the expectation that running `lafilefixer --justfixit' would stop |
| 29 |
revdep-rebuild from continuously finding a broken binutils? |
| 30 |
|
| 31 |
Or was I expected to run lafilefixer --justfixit and then rebuild |
| 32 |
binutils once more? |
| 33 |
|
| 34 |
In any case I did the later and now the oneshot has finished and a |
| 35 |
rerun of revdep-rebuild again finds the same `broken' binutils.... |
| 36 |
|
| 37 |
Apparently no progress has occurred.. |
Archives