This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/7646: Inclusion of X11 header files in to a C++ header, causes error messages during compilation.
- From: Phil Edwards <phil at jaj dot com>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 20 Aug 2002 19:06:00 -0000
- Subject: Re: c++/7646: Inclusion of X11 header files in to a C++ header, causes error messages during compilation.
- Reply-to: Phil Edwards <phil at jaj dot com>
The following reply was made to PR c++/7646; it has been noted by GNATS.
From: Phil Edwards <phil@jaj.com>
To: marcusma@lsl.co.uk
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/7646: Inclusion of X11 header files in to a C++ header, causes error messages during compilation.
Date: Tue, 20 Aug 2002 15:03:39 -0400
On Tue, Aug 20, 2002 at 10:05:39AM -0000, marcusma@lsl.co.uk wrote:
> >Environment:
> Solaris 8, running on a SparcUltra 10.
> >Description:
> causes the following error during compilation:
>
> /usr/openwin/include/X11/Xlib.h:2099: ISO C++ forbids declaration of `
> XSetTransientForHint' with no type
This is a Sun bug, documented in the GCC installation instructions.
> What would be useful, is a compiler flag that allows headers
> to be treated as C headers, not C++. It is imperative that the
> X11 headers can be included, and that the C++ compiles.
What would be even more useful is if you read the manual. :-) This flag
already exists, and is additionally documented alongside the Sun bug as
a workaround.
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002