public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: morandini@aero.polimi.it To: gcc-gnats@gcc.gnu.org Subject: libstdc++/6671: ext search path Date: Thu, 16 May 2002 01:06:00 -0000 [thread overview] Message-ID: <20020516080330.22924.qmail@sources.redhat.com> (raw) >Number: 6671 >Category: libstdc++ >Synopsis: ext search path >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: doc-bug >Submitter-Id: net >Arrival-Date: Thu May 16 01:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Marco Morandini >Release: gcc version 3.1 >Organization: >Environment: Suse linux 7.3 >Description: libstdc++, 5.4 Extensions and Backward Compatibility Although you can specify -I options to make the preprocessor search the g++-v3/ext..... This is wrong, because <ext/memory> will get loaded instead of <memory>, and <ext/memory> does not include ../memory Also, note that other files (ext/algorithm, ext/functional, ext/iterator, ext/numeric) suffer for a similar problem: for example, <ext/algorithm> include <algorithm>, and this will never be found with -I.../ext >How-To-Repeat: g++ -c -Igcc_include_path/g++-v3/ext pippo.C >Fix: a) fix the doc imposing the use of #include <ext/....> b) rename ext/memory (and the other files) c) Is there a way to include "../memory" if and only if ext/ is in the include search path? >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="pippo.C" Content-Disposition: inline; filename="pippo.C" #include <iostream> int main(void) { return 0; };
next reply other threads:[~2002-05-16 8:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-16 1:06 morandini [this message] 2002-05-19 8:48 paolo 2002-05-20 14:19 paolo
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=20020516080330.22924.qmail@sources.redhat.com \ --to=morandini@aero.polimi.it \ --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).