public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@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 12:16:00 -0000 [thread overview]
Message-ID: <20020820190600.15398.qmail@sources.redhat.com> (raw)
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
next reply other threads:[~2002-08-20 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 12:16 Phil Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-20 13:16 pme
2002-08-20 4:46 marcusma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020820190600.15398.qmail@sources.redhat.com \
--to=phil@jaj.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).