public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dan@graysonfamily.org
To: gcc-gnats@gcc.gnu.org
Cc: dan@math.uiuc.edu
Subject: c++/4464: cpp
Date: Wed, 03 Oct 2001 18:26:00 -0000	[thread overview]
Message-ID: <20011004011626.24963.qmail@graysonfamily.org> (raw)

>Number:         4464
>Category:       c++
>Synopsis:       cpp removes duplicate entries from include path
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 03 18:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Daniel R. Grayson
>Release:        3.0.1
>Organization:
>Environment:
System: Linux rhenium 2.4.9 #67 Mon Sep 3 11:10:40 CDT 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../configure  : (reconfigured) ../configure  : (reconfigured) ../configure --prefix=/usr : (reconfigured) ../configure  : (reconfigured) ../configure  : (reconfigured) ../configure --enable-shared --enable-threads=posix --prefix=/usr
>Description:

   cpp eliminates duplicate directories from the include path

   That can make #include_next fail, for example, the line 42 

	#include_next <wchar.h>

   from the file

	/usr/include/g++-v3/bits/std_cwchar.h


>How-To-Repeat:

    rhenium% cd /tmp
    rhenium% cat foo.cc
    #include <iostream.h>
    rhenium% g++ -c foo.cc
    rhenium% g++ -c -I/usr/include foo.cc
    In file included from /bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../include/g++-v3/bits/fpos.h:40,
		     from /bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../include/g++-v3/bits/std_iosfwd.h:41,
		     from /bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../include/g++-v3/bits/std_ios.h:39,
		     from /bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../include/g++-v3/bits/std_ostream.h:39,
		     from /bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../include/g++-v3/bits/std_iostream.h:40,
		     from /bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../include/g++-v3/backward/iostream.h:32,
		     from foo.cc:1:
    /bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.1/../../../../include/g++-v3/bits/std_cwchar.h:42:24: wchar.h: No such file or directory

    ... and so on ...

>Fix:

    cpp should not remove duplicate directories from the include path
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2001-10-03 18:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20011004011626.24963.qmail@graysonfamily.org \
    --to=dan@graysonfamily.org \
    --cc=dan@math.uiuc.edu \
    --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).