| 1 |
Grant Taylor wrote: |
| 2 |
> On 6/9/19 12:49 PM, Mick wrote: |
| 3 |
> |
| 4 |
>> 2. Sync portage and upgrade gcc to the latest stable version. Switch |
| 5 |
>> to it. |
| 6 |
> |
| 7 |
> Portage is within a few days of current. |
| 8 |
> |
| 9 |
> I do an emerge --sync -q before doing the emerge -DuNeq @world. I've |
| 10 |
> not done a --sync since then while working on things. The idea is to |
| 11 |
> not introduce any more changes while dealing with this. |
| 12 |
|
| 13 |
|
| 14 |
While I see that point and quite often it is a good idea, it could also |
| 15 |
be that a fix is in the newer tree. It could even be that you caught |
| 16 |
the tree in the middle of some sort of change and you missed part of it. |
| 17 |
|
| 18 |
If it were me, I'd try everything you can but if you can't find a |
| 19 |
solution, I'd sync and see what happens. I've had a fresh sync fix |
| 20 |
issues on a few occasions. It's somewhat rare but can happen. |
| 21 |
|
| 22 |
Just a thought. |
| 23 |
|
| 24 |
Dale |
| 25 |
|
| 26 |
:-) :-) |
Archives