public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jbakker@rssd.esa.int
To: gcc-gnats@gcc.gnu.org
Subject: c++/5997: CPLUS_INCLUDE_PATH not working properly
Date: Mon, 18 Mar 2002 08:16:00 -0000 [thread overview]
Message-ID: <20020318160635.17241.qmail@sources.redhat.com> (raw)
>Number: 5997
>Category: c++
>Synopsis: CPLUS_INCLUDE_PATH not working properly
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Mar 18 08:16:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Jorgo Bakker
>Release: gcc version 3.0.4
>Organization:
>Environment:
sparc-sun-solaris2.8, sparc-sun-solaris2.7, sparc-sun-solaris2.6
i486-suse-linux (Linux 2.4.10-64GB-SMP)
>Description:
With the introduction of GCC 3, usage of CPLUS_INCLUDE_PATH seems to be valid for C-headers only.
Is this ever repaired?
>How-To-Repeat:
tar xzf foo.tgz
CPLUS_INCLUDE_PATH=`pwd`/include c++ -c main.cc ; echo $?
>Fix:
Workaround: c++ -c -Iinclude main.cc
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="foo.tgz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="foo.tgz"
H4sIAI8PljwAA+3VwUrEMBAG4J7zFMP2sntZJ27SHPZhpDYpjVtT6LZexHc3XeNhRRSEVMH/u0wa
ApkwHcaHpp+tuykyYlZstI6R2Rh1iVK9xaRgo5RWXB10XMtb1rIgnTOpd/N5qkei4uG+Pp3c+MU5
N57XSGhdPtW/HYZ9l+kOlsxVqvdn9Zfy8LH+xuiCOFM+V/55/UvfButaivW/60QZlz649CWeBm+p
q4Pt3daHaXe82mn7oV72ROmC9a347afADzzWPuybJusd3/U/L7Mh9b+SMp6XlVbo/zWUaQDQ5jIB
NkLERqflr9juxLMgGt00j4H4KF7Q4QAAAAAAAAAAAAAAAAAAAH/TK4qj458AKAAA
next reply other threads:[~2002-03-18 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 8:16 jbakker [this message]
2002-03-18 10:26 Neil Booth
2002-03-18 11:16 Zack Weinberg
2002-03-18 11:36 Neil Booth
2002-03-19 1:16 Jorgo Bakker
2002-03-19 1:36 Zack Weinberg
2002-03-19 2:06 Jorgo Bakker
2002-03-19 11:46 Neil Booth
2002-03-20 2:16 Jorgo Bakker
2002-03-20 10:15 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=20020318160635.17241.qmail@sources.redhat.com \
--to=jbakker@rssd.esa.int \
--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).