🚀 go-pugleaf

Well, since I brought something like this up a few days ago - I guess I'll
summarize what I've found out.  It is my opinion that although the MIT X
Consortium recommends the use of gcc to build the whole shebang, I don't
think they mean gcc-2.2.2!!

I have had numerable problems building the server successfully, and when I
actually did get the thing to build it was so ____ed that all the fonts 
appeared backwards!  This problem was originally reported to me by Vivek 
Singhal at UT/Austin.  Anyway, the solution I'm using right now is to build
the whole environment using gcc, and then building the server using the local
flavor of cc.

As to your problem, Rich, I seem to remember an option in the configuration
of gcc that takes care of broken alloca() calls - have a look see.

The whole reason why I started to try the gcc path was that subsequent client
builds using the cc-compiled R5 environment were crapping out for various 
reasons.  I'm hoping that now this will have fixed things. (Stay tuned).

-- 
-------------------------------------------------------------------------------
Paul A. Scowen				INTERNET: scowen@wfpc3.la.asu.edu
Department of Physics & Astronomy		  uk1@spacsun.rice.edu
Arizona State University		Tel:      (602) 965-0938
Tempe, AZ 85287-1504			FAX:      (602) 965-7954
-------------------------------------------------------------------------------