From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15413 invoked by alias); 20 Aug 2002 19:06:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 15399 invoked by uid 71); 20 Aug 2002 19:06:00 -0000 Date: Tue, 20 Aug 2002 12:16:00 -0000 Message-ID: <20020820190600.15398.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Phil Edwards Subject: Re: c++/7646: Inclusion of X11 header files in to a C++ header, causes error messages during compilation. Reply-To: Phil Edwards X-SW-Source: 2002-08/txt/msg00418.txt.bz2 List-Id: The following reply was made to PR c++/7646; it has been noted by GNATS. From: Phil Edwards 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