🚀 go-pugleaf

In article <1993Mar12.133522.1211@iiasa.ac.at>
marek@iiasa.ac.at (Marek  MAKOWSKI) writes:
|> The gcc 2.3.3. cleanly installed on the Sun Sparc, generates several warnings
|> of the type:
|> /usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.3.3/include/unistd.h:53: warning: text following `#endif' violates ANSI standard
|> In file included from /usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.3.3/include/unistd.h:73, from com_a.c:5:
|> /usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.3.3/include/sys/types.h:30: warning: text following `#endif' violates ANSI standard
|> 
|> - the program was compiled with flags:
|> gcc -c -g -ansi -pedantic -Dsparc -W -Wall -Wpointer-arith -Wshadow -DUNIX -DSUN com_a.c
|> 
|> I would appreciate an advise on how to fix the problem (without a manual
|> modification of *.h files).
|> Thanks in advance for your help/fix.

The include files that you mention are generated by fixincludes, a part
of the distribution. This is basically a wrapper around a gigantic sed
script to fix up the known problems. Previously this sed placed /* and
*/ around any text after #else and #endif but this has been commented
out. So the answer to your question is that you can simply reinstate
those line and run fix includes again however:

Fri Mar  6 00:30:10 1992  Richard Stallman  (rms@mole.gnu.ai.mit.edu)

        * fixincludes: Don't fix comments on #endif, #else.
        It made the egrep string too long.

-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm