Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!ANDREW.CMU.EDU!dl2n+
From: dl2n+@ANDREW.CMU.EDU (Daniel Edward Lovinger)
Newsgroups: comp.windows.x
Subject: Re: xterm on sun3
Message-ID: <sZnZOWa00WB6AqLEMv@andrew.cmu.edu>
Date: 6 Feb 90 04:46:26 GMT
References: <EZnXeSq00WB9AX=bZi@andrew.cmu.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 21

With the assistance of a line eater, I write (in a previous message) :
>> This is done on a sun 3/60, with display device /dev/cgfour0, and
>> running SunOS 4.0, and, by the way, using X11R4 (with the patches1
>> installed). I built X11R4 (and so, xterm as well) using gcc1.36,
>> with the fixes included for gcc1.36 building X11R4. Everything else 
>> seems to work fine with regards to xterm.
>
>        Gcc 1.36 is your problem. I built the release (no fix-1) under
>gcc 1.36 and got the exact behavior you describe. A rebuild with Sun
>0S 4.0.3 cc -O2 has yet to give me any problems, however.
>
>        Suggestion - wait for gcc 1.37, or back out your version of
>gcc to 1.35. Something is tripping one of the few remaining bugs in
>there somewhere.

	I am refering to an xterm coredump when the TEK window is
requested. Sorry for the confusion ...


Dan Lovinger
CMU Architecture