public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: f_ker@yahoo.co.uk
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/6076: cross-compiled libcpp handles CPLUS_INCLUDE_PATH wrong
Date: Wed, 27 Mar 2002 19:36:00 -0000	[thread overview]
Message-ID: <20020328032729.10228.qmail@sources.redhat.com> (raw)


>Number:         6076
>Category:       preprocessor
>Synopsis:       cross-compiled libcpp handles CPLUS_INCLUDE_PATH wrong
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 27 19:36:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     f_ker@yahoo.co.uk
>Release:        3.0.4
>Organization:
>Environment:
host=build=i686-pc-linux-gnu
target=arm-thumb-elf
>Description:
Putting any file with templates in it in the CPLUS_INCLUDE_PATH and running it through (in my case) the arm-thumb-elf-g++ libcpp on host i686-pc-linux-gnu (gcc 3.0.4) produces an error "template with C linkage" pointing to declaration of templatised class.

>How-To-Repeat:
Put the following in a file (lets call it dummy.hh):
template<typename T>
struct Dummy
{
};

Put dummy.hh somewhere in CPLUS_INCLUDE_PATH (but not in current directory)

Put the following in another file (lets call it main.cc):
#include <dummy.hh>

do a 'arm-thumb-elf-g++ main.cc'.

Error:
In file included from main.cc:1:
/home/foobar/include/dummy.hh:2: template with C linkage


As far as I know, it only gives an error when using 'arm-thumb-elf-g++' on 'i686-pc-linux-gnu' host/build.  But when using native 'i686-pc-linux-gnu-g++', all is well and dandy.  Very strange.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-03-28  3:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 19:36 f_ker [this message]
2002-04-09 18:05 rth

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=20020328032729.10228.qmail@sources.redhat.com \
    --to=f_ker@yahoo.co.uk \
    --cc=gcc-gnats@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).