Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!ginosko!gem.mps.ohio-state.edu!apple!sun-barr!lll-winken!gauss.llnl.gov!casey
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: Re: X11.3 on alliant with fx/c
Keywords: alliant support X11 compilation
Message-ID: <36535@lll-winken.LLNL.GOV>
Date: 22 Oct 89 22:04:15 GMT
References: <125@euteal.ele.tue.nl>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@gauss.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 17


  Well, you certainly had a lot of problems getting X.V11R3 up.  I
suggest you try again, but this time with GCC.  It works a lot better.
Alliant's C compiler is fundamentally worthless.  You can never tell when
it's going to compile something correctly.  GCC is a lot more robust.

  Also, one item you listed as a C usage bug in X.V11R3, semicolons
following function definitions, is perfectly legal (though disgusting)
C.  It forms an empty C declaration.

  You can get the patches to make GCC work on the Alliant from Eugene
Brooks (brooks@maddog.llnl.gov) if they're not already in the main GCC
distribution (I don't keep up with it, so I don't know).  I can send you
what little I had to do to get X.V11R3 up on the Alliant (the same code
works under both Concentrix 4.0 and 5.0).

Casey