This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
libstdc++/6671: ext search path
- From: morandini at aero dot polimi dot it
- To: gcc-gnats at gcc dot gnu dot org
- Date: 16 May 2002 08:03:30 -0000
- Subject: libstdc++/6671: ext search path
- Reply-to: morandini at aero dot polimi dot it
>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;
};