From: Joe Buck <jbuck@synopsys.com>
To: "Altenau,
Maureen D "CECOM RDEC C2D
<Maureen.Altenau@mail1.monmouth.army.mil>
Cc: gcc@gcc.gnu.org
Subject: RE: C linkage when using C++
Date: Thu, 06 Dec 2001 16:47:00 -0000 [thread overview]
Message-ID: <1007684986.11909.5.camel@trimaran> (raw)
In-Reply-To: <EF40D5BF9C48D411AA8E0008C7913EFB53F37A@mail15.monmouth.army.mil>
On Tue, 2001-12-04 at 07:17, Altenau, Maureen D CECOM RDEC C2D wrote:
> Hi,
>
> I have attached two of the files that are creating errors. The error I get
> is
> "Template with C Linkage". For some reason, the compiler thinks there is C
> Linkage, which if that is the case, causes certain C++ features to be
> flagged as errors. This is the case with templates. This is the first time
> I have used g++. I thought that I may need to set a compiler option or a
> compiler directive to tell the compiler that there is no c linkage. I did
> not see anything in the code such as extern "C" to indicate C linkage.
Sorry, but this isn't a complete test case: the command line isn't given
and there are some headers that aren't included. Because of this I
can't duplicate the error. Please file a complete bug report; you can
find instructions on http://gcc.gnu.org/. Please remember that in order
to help you, someone has to be able to duplicate *exactly* what you did.
The easiest way to make sure that all needed sources are present is to
send preprocessor output; also don't forget to send the exact command
line you typed and the exact error messages you got, not a paraphrase.
next parent reply other threads:[~2001-12-07 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EF40D5BF9C48D411AA8E0008C7913EFB53F37A@mail15.monmouth.army.mil>
2001-12-06 16:47 ` Joe Buck [this message]
2001-12-03 9:48 Altenau, Maureen D CECOM RDEC C2D
2001-12-03 12:05 ` Joe Buck
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=1007684986.11909.5.camel@trimaran \
--to=jbuck@synopsys.com \
--cc=Maureen.Altenau@mail1.monmouth.army.mil \
--cc=gcc@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).