🚀 go-pugleaf

In <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?

I encountered this problem only after installing the 3.2.4 (current version 
of the) development system.  GCC seemed to work fine with the version 3.2.2 
header files.  So, what I did was copy all the version 3.2.2 header files to a 
directory such as /usr1/include -- leaving all the 3.2.4 header files in 
their usual places.  I was then able to compile with the following command:
% gcc -nostdinc -I/usr1/include ... etc.
This only works if you have the 3.2.2 development system.

Curtis Olson        (olson@cs.umn.edu)

--
   .
--o0o--  Curtis Olson     (olson@cs.umn.edu)