public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: wolf359_@gmx.net To: gcc-gnats@gcc.gnu.org Subject: preprocessor/3413: include_next does not work with -I/usr/include Date: Mon, 25 Jun 2001 12:36:00 -0000 [thread overview] Message-ID: <20010625192838.32746.qmail@sourceware.cygnus.com> (raw) >Number: 3413 >Category: preprocessor >Synopsis: include_next does not work with -I/usr/include >Confidential: no >Severity: serious >Priority: high >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Mon Jun 25 12:36:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Thomas Weidner >Release: 3.0.1 (20010625) >Organization: >Environment: i686 Linux2.4.5 glibc2.2.2 >Description: cpp reports the following error when processing a source file and using -I/usr/include (see How-To-Repeat): In file include from /usr/local/include/g++-v3/cstring:31, from 1.cpp:1: /usr/local/include/g++-v3/bits/std_cstring.h:40:25: string.h: file not found KDE doesn't compile because of this ! >How-To-Repeat: echo "#include <cstring>" >1.cpp cpp 1.cpp -I/usr/include >/dev/null >Fix: don't know,perhaps let include_next ALWAYS search /usr/include as last directory,even if it was given with -I >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-25 12:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-25 12:36 wolf359_ [this message] 2001-06-25 13:34 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=20010625192838.32746.qmail@sourceware.cygnus.com \ --to=wolf359_@gmx.net \ --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: linkBe 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).