[RE: [lug] Locking up during compile]

[Chip Atkinson]

Chris is right.  It may be the memory settings.  I had problems with what
I thought was a Cyrix chip, but it turned out to be bad memory.  Of course
I found that out _after_ getting an Intel chip.

Chip

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 Chip Atkinson 
 http://www.pupman.com 
 --- If I can't fix it, I can fix it so it can't be fixed --
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

On 16 Oct 1999, Justin wrote:

> Chris M <chrism at peakpeak.com> wrote:
> > >My experience and from what I've seen on this list indicate some hardware
> > >problems.  If the L2 cache disabling doesn't work, start swapping out
> > >memory, etc.
> > >
> > >Chip
> > 
> > Well, I'd not swap memory just yet.
> > 
> > First step should be to introduce more wait states to see if memory 
> > speed is the issue.  BIOS will allow you to do this usually.
> > 
> > But on the Cyrix processors, make sure that you have a "friendly" 
> > version of gcc.  I've seen versions of gcc that would SEGV or signal 
> > 11 incorrectly, but backing up to an earlier rev worked fine. But if 
> > it happens on both processors try the wait states.
> > 
> > On AMD chips it's yet another problem sometimes :)
> > 
> > Chris
> > Peak to Peak Internet
> > http://www.peakpeak.com
> > 
> 
> Yes, someone else suggested going back to an earlier gcc version. Would it be
> safe to rpm up say...my gcc from Redhat 5.2 or 6.0 maybe? Hopefully I can test
> this stuff tonight when I get home from work. Thanks for help.
> 
>              Justin
> 
> ____________________________________________________________________
> Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>