From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2844 invoked by alias); 7 Dec 2001 00:26:20 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 2820 invoked from network); 7 Dec 2001 00:26:19 -0000 Received: from unknown (HELO localhost.localdomain) (146.225.1.61) by sources.redhat.com with SMTP; 7 Dec 2001 00:26:19 -0000 Received: (from jbuck@localhost) by localhost.localdomain (8.11.6/8.11.6) id fB70TkE13594; Thu, 6 Dec 2001 16:29:46 -0800 X-Authentication-Warning: localhost.localdomain: jbuck set sender to jbuck@synopsys.com using -f Subject: RE: C linkage when using C++ From: Joe Buck To: "Altenau, Maureen D "CECOM RDEC C2D Cc: gcc@gcc.gnu.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0 (Preview Release) Date: Thu, 06 Dec 2001 16:47:00 -0000 Message-Id: <1007684986.11909.5.camel@trimaran> Mime-Version: 1.0 X-SW-Source: 2001-12/txt/msg00335.txt.bz2 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.