------- Comment #12 from burnus at gcc dot gnu dot org 2010-05-02 14:32 -------
(In reply to comment #11)
> Consensus seems to be: no, do not search the system include paths.
>
> Set status to WAITING. To be closed as INVALID(?) in three months from now if
> there is no further discussion.
>
Shall this be noted in the man page? It currently reads as follows which
implies that "include" and "#include" are strongly tied?
-Idir
These affect interpretation of the "INCLUDE" directive (as well as
of
the "#include" directive of the cpp preprocessor).
Also note that the general behavior of -I and "INCLUDE" is pretty
much the same as of -I with "#include" in the cpp preprocessor, with
regard to looking for header.gcc files and other such things.
This path is also used to search for .mod files when previously
compiled modules are required by a "USE" statement.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707
