🚀 go-pugleaf

Hello,

I am developing an application to run on a Sun SPARCstation with
OpenWindows 3.0, using GNU CC.  The OpenWindows header files claim to
be ANSI-compatible, but whenever they are referenced with the
"-pedantic" switch the following messages result:

[...]
/usr/include/pixrect/pixrect.h:104: warning: text following #else or #endif violates ANSI standard
/usr/include/pixrect/pixrect.h:121: warning: text following #else or #endif violates ANSI standard
/usr/include/pixrect/pixrect.h:125: warning: text following #else or #endif violates ANSI standard
[...]

I want to continue using the "-pedantic" switch, so that the code
remains portable to other ANSI compilers, but getting around seventy
(!) of these messages for *each* file being compiled makes it very easy
to miss messages of more importance.  I cannot leave my terminal while
the system is building, or I will have to go back and scan through
thousands of lines of warning messages to see whether anything else
came through.

Is there any way to disable a *particular* warning message in GNU CC,
such as this one in particular?  This would provide the desired level
of checking, without an overwhelming amount of (from our point of view
as users of OpenWindows) unnecessary and repetitive information.

The only other solution would be to change the OpenWindows files on any
machine that might be used to build the system, but we certainly don't
want to take on the burden of supporting this modification ourselves.
Perhaps Sun will release a new set of header files that do not have
this problem, as they did with the release of OpenWindows 3.0.  Until
then, however, I need an effective solution to this problem.
____________________________________________________________________________
Daniel A. Harling                        (harling@pictel.com)
PictureTel Corp.             Opinions expressed are not necessarily those of
Peabody, MA  01960                 PictureTel, but they ought to be!