public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Berthold Höllmann" <hoel@germanlloyd.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7327: -isystem and template linkage Date: Tue, 13 Aug 2002 07:06:00 -0000 [thread overview] Message-ID: <20020813115602.28166.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7327; it has been noted by GNATS. From: =?ISO-8859-15?Q?Berthold_H=F6llmann?= <hoel@germanlloyd.org> To: <neil@gcc.gnu.org> Cc: <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/7327: -isystem and template linkage Date: 13 Aug 2002 13:52:50 +0200 neil@gcc.gnu.org writes: > Old Synopsis: strange error through using -isystem > New Synopsis: -isystem and template linkage >=20 > State-Changed-From-To: open->analyzed > State-Changed-By: neil > State-Changed-When: Tue Aug 13 04:12:48 2002 > State-Changed-Why: > One way gives your headers extern "C" wrappers, the other > doesn't. I'm not sure what the fix is, or even if it should be fixed. >=20 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D= g cc&pr=3D7327 >=20 If I generate the preprocessed files using g++ -E -isystem /home/hoel/work/boost/boost err.cxx -o erra and g++ -E -I /home/hoel/work/boost/boost err.cxx -o errb and call=20 diff err? | grep -v "^[<>] #" | grep -v "\---" afterwards, the only output are the different lines. So why are the C++ lines wrapped extern "C" using -isystem but not using -I? I'm also not sure what the fix is, but shure it should be fixed. Greetings Berthold --=20 Dipl.-Ing. Berthold H=F6llmann __ Address: hoel@germanlloyd.org G / \ L Germanischer Lloyd phone: +49-40-36149-7374 -+----+- Vorsetzen 32/35 P.O.Box 111606 fax : +49-40-36149-7320 \__/ D-20459 Hamburg D-20416 Hamburg This email contains confidential information for the exclusive attention of the intended addressee. Any access of third parties to this email is unauthorized. Any use of this email by not intended recipients like copying, distribution, disclosure etc. is prohibited and may be unlawful. When addressed to our clients the content of this email is subject to the General Terms and Conditions of GL's Group of Companies applicable at the date of this email.=20 GL's Group of Companies does not warrant and/or guarantee that this message at the moment of receipt is authentic, correct and its communication free of errors, interruption etc.=20
next reply other threads:[~2002-08-13 11:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-13 7:06 Berthold Höllmann [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-21 21:36 Patrick Frants 2002-11-03 20:26 Ben Hines 2002-10-12 12:04 abrahams 2002-08-13 4:56 neil
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=20020813115602.28166.qmail@sources.redhat.com \ --to=hoel@germanlloyd.org \ --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: linkBe 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).