https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707
Bug 35707 depends on bug 49138, which changed state.
Bug 49138 Summary: Add /usr/include/fortran/{,gcc-} to the file/module
search path
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49138
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707
--- Comment #17 from Dominique d'Humieres ---
*** Bug 49138 has been marked as a duplicate of this bug. ***
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707
--- Comment #16 from Dominique d'Humieres ---
(In reply to comment #15)
> (In reply to Daniel Franke from comment #13)
> > Yes, I think that this text needs an update.
>
> I concur that we - still - need a better documentation on this.
> It's rel
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707
Tobias Burnus changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Depends on|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
--- Comment #13 from dfranke at gcc dot gnu dot org 2010-05-09 19:41
---
(In reply to comment #12)
>-Idir
>These affect interpretation of the "INCLUDE" directive (as well as
> of
>the "#include" directive of the cpp preprocessor).
>
>Also not
--- 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.
>
--- Comment #11 from dfranke at gcc dot gnu dot org 2010-05-02 14:03
---
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.
--
dfranke at gcc dot gnu dot or
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last recon
--- Comment #10 from dfranke at gcc dot gnu dot org 2009-01-03 23:26
---
(In reply to comment #7)
> Good question. FX and Joe don't like the idea, but Fortran files (".h"/".inc"
> and ".mod" files one can find in /usr/include in some Linux distributions.
Whoever requires .mod files pro
--- Comment #9 from mikael at gcc dot gnu dot org 2008-12-08 14:25 ---
(In reply to comment #7)
> A semi-proper place for .mod files is:
> /usr/lib64/gcc/x86_64-suse-linux/4.4/finclude/
> (Semi because finclude does not distinguish between e.g. 32bit and 64bit.)
>
Isn't (...)/x86_64-(
--- Comment #8 from dfranke at gcc dot gnu dot org 2008-12-08 12:50 ---
> A semi-proper place for .mod files is:
> /usr/lib64/gcc/x86_64-suse-linux/4.4/finclude/
> (Semi because finclude does not distinguish between e.g. 32bit and 64bit.)
One could argue that .mod files are library su
--- Comment #7 from burnus at gcc dot gnu dot org 2008-12-08 11:33 ---
(In reply to comment #6)
> To add the default paths defined in gcc/cppdefault.c (cpp_include_defaults) to
> the module/INCLUDE search path, one could clone gcc/incpath.c
> (add_standard_paths) and call gfc_add_include
--- Comment #6 from dfranke at gcc dot gnu dot org 2008-12-07 19:38 ---
Since libcpp integration, default search paths (i.e. /usr/local/ etc.) are used
for #include'd files.
To add the default paths defined in gcc/cppdefault.c (cpp_include_defaults) to
the module/INCLUDE search path, on
--- Comment #5 from dfranke at gcc dot gnu dot org 2008-08-18 20:56 ---
Reminder: libbackend.a(cpp_include_defaults) seems to be the place where
standard include paths for targets are available -- including, but not limited
to, /usr/include.
--
http://gcc.gnu.org/bugzilla/show_bug.c
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2008-05-14 10:48
---
(In reply to comment #3)
> Fortran files should not be put into /usr/local/include or /usr/include. Those
> directories are defined for C headers. It is particularly bad to put binary
> files there.
You're confus
--- Comment #3 from jkrahn at nc dot rr dot com 2008-05-08 18:19 ---
Fortran files should not be put into /usr/local/include or /usr/include. Those
directories are defined for C headers. It is particularly bad to put binary
files there. We should instead develop a standard location for F
--- Comment #2 from dfranke at gcc dot gnu dot org 2008-04-06 00:20 ---
Related: PR35055
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707
--- Comment #1 from dfranke at gcc dot gnu dot org 2008-03-28 23:19 ---
Implementation of this request should be trivial. IIRC just add the paths as
arguments to -I options in lang-spec.h.
> That way one could also cpp-preprocess files included via "INCLUDE"
> rather than via "#includ
19 matches
Mail list logo
