This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

libstdc++/6671: ext search path

>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
>Originator:     Marco Morandini
>Release:        gcc version 3.1
Suse linux 7.3
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
g++ -c -Igcc_include_path/g++-v3/ext pippo.C
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?
Content-Type: text/plain; name="pippo.C"
Content-Disposition: inline; filename="pippo.C"

#include <iostream>

int main(void) {
	return 0;

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]