On Mon, 06 Jun 2005 22:35:56 GMT, "Darren" <darren@notathome.net> wrote:
> >
> > http://www.mklab.rhul.ac.uk/~tom/codeviz_build.log
^^^^^^^^^^^^^^^^^-- gzip the
thing next time, please?: 785982 --> 55518 bytes. Put in content
negotiation and browsers will decompress on the fly (excepting of
course, the evil empire's msie
> >
> > how does this compare with yours?
> I'll put my log on on my web site when i get it running
> If possible you might want to upgrade to slack 10.1. Thats what i built mine
> on.

Mine built okay on slack-10.1 too, but OP putting the _entire_ build.log
including 'wget' of the gcc source has somewhat soured my perspective,
perhaps OP the cleaner, playing on a box somebody left on? )

On topic:
Compiling a compiler is a big task, is the box a little tired? Need dust
bunnies removed, CPU cooling, those sort of things? The compiler error
message is hopelessly vague Doesn't convey much to me...

Though problem may be where you not looking. OP do much CPU intensive
stuff on it? Compiling large jobs --> lots of files read/written, all
CPU, memory in use. "The" way to test hardware. If OP trust h/w, maybe
time for update?

--Grant.