🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.gcc.help
Article #755

Re: Problems building GCC on SCO systems

#755
From: Colin Smiley
Date: Thu, 10 Dec 1992 21:23
54 lines
3145 bytes
In article <9212071040.AA10051@noa.csrl.aoyama.ac.jp> rms@noa.csrl.aoyama.ac.jp (Richard Stallman) writes:

   There are problems building GCC on recent SCO systems.  Several people
   have found an apparent solution of defining STDC_VALUE as 0.  This
   appears to work, but it is actually incorrect because it causes GCC to
   define __STDC__ as 0 *all the time*.

   This is incorrect because GCC is supposed to handle __STDC__ the same
   way on all machines: namely, it should be 1.

   The reason people are tempted to make this change is that the SCO
   header files expect __STDC__ to be 0, and get confused if it isn't.
   However, fixincludes is supposed to change the conditionals in the
   header files so they will work properly with __STDC__ == 1.  So the
   problem should be limited to the compilation of GCC itself.

   Can anyone find a way around this problem which alters only the
   compilation of GCC and does not alter what GCC does when installed?


Here is what I did to get GCC to work on a SCO3.2v4 box...

I first happened upon the idea of changing "X_CFLAGS= -D__STDC__=0" to
"X_CFLAGS= -U__STDC__" in ./config/x-i386s4.  This worked fine for
building the initial stage with rcc.  I soon found out that this was a
bad idea when I tried to make the stage1 compiler.  The SCO assembler
would bail out while working on core.c and I could get no furthur.

I then tried defining "X_CFLAGS = -DSTDC_VALUE=0".  This worked just
fine and GCC compiled with a good result from "make compare".  After
installing GCC, I used fixincludes.svr4 instead of the regular
fixincludes, and all I had to do was create syslimits.h (Which I stole
from a bad install of GCC 2.3.1, but with a successful fixincludes).
Everything seems to be working fine and I have been getting all sorts
of other tools that I have been suffering without to compile.

Hope some of that helped...


Colin

P.S. While I am in the compiling mood, has anyone gotten X11R5 to
compile on a SCO 3.2.4 box (No, we do not have ODT on many of our
machines)?


--
-------------------------------------------------------------------------
Colin Smiley, Compaq Computer Corporation, Houston, Texas 77269-2000
e-mail: smiley@compaq.com                           Phone: (713) 378-8426
-------------------------------------------------------------------------
Disclaimer:  Any opinions expressed here do not reflect the opinions of
Compaq Computer Corp.  They make computers.  I make noise.
Technical Details
Message-ID: <SMILEY.92Dec10162349@akasha.eng.hou.compaq.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!cs.utexas.edu!wotan.compaq.com!twisto.eng.hou.compaq.com!twisto!smiley
References: <9212071040.AA10051@noa.csrl.aoyama.ac.jp>

Show Full Headers
Complete Article Headers
Newsgroups: gnu.gcc.help
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!cs.utexas.edu!wotan.compaq.com!twisto.eng.hou.compaq.com!twisto!smiley
From: smiley@akasha.eng.hou.compaq.com (Colin Smiley)
Subject: Re: Problems building GCC on SCO systems
In-Reply-To: rms@noa.csrl.aoyama.ac.jp's message of Mon, 7 Dec 1992 10: 40:05 GMT
Message-ID: <SMILEY.92Dec10162349@akasha.eng.hou.compaq.com>
Sender: news@twisto.eng.hou.compaq.com (Netnews Account)
Organization: Compaq Computer Corporation
References: <9212071040.AA10051@noa.csrl.aoyama.ac.jp>
Distribution: gnu
Date: Thu, 10 Dec 1992 21:23:49 GMT
Lines: 55