| 1 |
On Monday 24 Apr 2017 21:09:36 Grant Edwards wrote: |
| 2 |
> On 2017-04-24, Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 3 |
> > On Monday 24 Apr 2017 16:45:58 I wrote: |
| 4 |
> >> On Monday 24 Apr 2017 14:47:32 Mick wrote: |
| 5 |
> >> > I've had the odd rebuild failure here & there, don't bother |
| 6 |
> >> > re-emerging |
| 7 |
> >> > it until revdep-rebuild has finished. Any dependencies it needs |
| 8 |
> >> > would |
| 9 |
> >> > have been rebuilt by then and it should complete without problem. |
| 10 |
> >> |
| 11 |
> >> Quite so, but it was an internal compiler error, so that may not help. |
| 12 |
> >> I'll remerge it when the machine's quiet and see. |
| 13 |
> > |
| 14 |
> > It did help. It's emerged okay. |
| 15 |
> |
| 16 |
> In my experience, internal GCC errors that show up intermittently |
| 17 |
> and/or only under heavly load usually means failing RAM (or more |
| 18 |
> rarely, some other hardware problem: something bad on the PCI bus, |
| 19 |
> failing swap parition, etc.). |
| 20 |
> |
| 21 |
> I'd run memtest86 overnight, if I were you... |
| 22 |
|
| 23 |
Oo-er! I hope it's not that: this box is only just out of guarantee. |
| 24 |
|
| 25 |
-- |
| 26 |
Regards |
| 27 |
Peter |
Archives