public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@stanford.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/1688: Includes causing extern "C" not to behave correctly (?)
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <20010118214606.5842.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c++/1688; it has been noted by GNATS.
From: "Zack Weinberg" <zackw@stanford.edu>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: daniel@ncsu.edu, gcc-gnats@gcc.gnu.org
Subject: Re: c++/1688: Includes causing extern "C" not to behave correctly (?)
Date: Thu, 18 Jan 2001 12:30:00 -0800
On Thu, Jan 18, 2001 at 07:59:46PM +0000, Neil Booth wrote:
> Zack Weinberg wrote:-
>
> > So the complaint is that in
> >
> > #include <X11/Xlib.h>
> >
> > the header is treated as a system header without -I/usr/openwin/include,
> > and as a user header with the switch? Did the user want it to be
> > treated as a user, or system header?
>
> Yes. I think Daniel wants it treated as a system header. Like you
> say, I think this is easy to solve - I wasn't thinking.
It occurs to me that he might want the implicit extern "C" behavior.
Unfortunately, unlike all the other effects of system-headerness, that
is not triggered by -isystem, and there's no way to get it on the
command line. It wouldn't be hard to add a switch; I never did
primarily because I couldn't think of an appropriate name.
Leaving out the -I altogether may be your best bet, Daniel. I don't
know where it's coming from - Imake? If so, that can be edited out of
the imake templates (in /usr/openwin/lib/X11/config, probably).
zw
>From magfr@lysator.liu.se Sun Apr 01 00:00:00 2001
From: Magnus Fromreide <magfr@lysator.liu.se>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/2440&Body=http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2440&database=gcc
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010331192600.31549.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg02694.html
Content-length: 865
The following reply was made to PR c++/2440; it has been noted by GNATS.
From: Magnus Fromreide <magfr@lysator.liu.se>
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org,
ian.wakeling@knightfisk.com
Cc:
Subject: Re: c++/2440&Body= http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view& ;
pr=2440&database=gcc
Date: Sat, 31 Mar 2001 21:20:24 +0200 (MET DST)
I do suppose I am responsible for the sstream for 2.95.*.
I would like to know what version of sstream you have used.
There should be a line in the file sstream that reads
* Written by Magnus Fromreide (magfr@lysator.liu.se). */
Unless the line following that one reads
/* seekoff and ideas for overflow is largely borrowed from libstdc++-v3 */
you would be well adviced to fetch a new version from
http://gcc.gnu.org//cgi-bin/cvsweb.cgi/~checkout~/gcc/libstdc++/Attic/sstream?rev=1.2
/MF
next reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 0:00 Zack Weinberg [this message]
2001-04-01 0:00 Neil Booth
2001-04-01 0:00 c++/1688: Includes causing extern "C" not to behave correctly(?) Daniel Henninger
2001-04-01 0:00 c++/1688: Includes causing extern "C" not to behave correctly (?) Neil Booth
2001-04-01 0:00 Phil Edwards
2001-04-01 0:00 daniel
2001-04-01 0:00 Neil Booth
2001-04-01 0:00 Zack Weinberg
2001-04-01 0:00 c++/1688: Includes causing extern "C" not to behave correctly(?) Daniel Henninger
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=20010118214606.5842.qmail@sourceware.cygnus.com \
--to=zackw@stanford.edu \
--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).