No, only since I applied the patches to fix inode.c and the other
part for USB. Every time I ran make though, it died at this
exact same place.
Thus spake Vojtech Pavlik ([EMAIL PROTECTED]):
> On Thu, Apr 13, 2000 at 01:57:01PM -0600, Robert L. Harris wrote:
>
> > The diagnostics according to prom show it at 63degrees. It's
> > not over clocked or anything.
> >
> > Still a possibility?
>
> Yes. Some CPUs are only guaranteed to work to 60, some to 85, supposing
> that's degrees Celsius. Could you try having your computer case open
> while compiling?
>
> Anyway, does this happen everytime you compile the source? If yes, it
> could really be a bug in the compiler or a corrupt compiler binary.
>
> But this is usually (that doesn't mean it's your case) either bad RAM
> (or running above its specs), overheated cpu/cache or bad harddrive cable.
>
> --
> Vojtech Pavlik
> SuSE Labs
:wq!
---------------------------------------------------------------------------
Robert L. Harris | Microsoft:
Senior System Engineer | For when quality, reliability
at RnD Consulting | and security just aren't
\_ that important!
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
FYI:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
