Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!mcnc!duke!romeo!ndd
From: ndd@romeo.cs.duke.edu (Ned D. Danieley)
Newsgroups: comp.windows.x
Subject: Re: problems compiling R3 on 4/280
Summary: done!
Keywords: X11R3
Message-ID: <13724@duke.cs.duke.edu>
Date: 3 Mar 89 14:28:43 GMT
References: <13578@duke.cs.duke.edu> <13678@duke.cs.duke.edu>
Sender: news@duke.cs.duke.edu
Lines: 26

In article <13678@duke.cs.duke.edu>, ndd@romeo.cs.duke.edu (Ned D. Danieley) writes:
> In article <13578@duke.cs.duke.edu>, ndd@romeo.cs.duke.edu (Ned D. Danieley) writes:
> > I just tried to compile X11R3 on a Sun 4/280 running SunOs 4.0, using
> > gcc 1.31. Several modules failed compilation with signal 11 or signal
> > 6 (lib/X/GetPRoot.c, server/dix/colormap.c, server/ddx/mi/milines.c,
> > etc.). I have applied patches 1 through 8, and the Purdue 2.0 speedups.
> > I didn't have any trouble on my 3/280 running 3.5.
> > 
> > Has anyone else seen this? If so, how can I get around it? Is gcc 1.33
> > useful?
> > 
> 
> I haven't seen an answer to this yet, so I'll try again. Has anyone

Okay, I got several answers. It turns out that gcc 1.33 works just
fine, with the exception of oscolor.c and rgb. I suspect that these would
work, too, if I had applied the dbm fix suggested in the Purdue
speedup notes.

Thanks to all who replied.

ned



(count these lines)