This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/35707] Search /usr/local/include and /usr/include for .mod files
- From: "mikael at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Dec 2008 14:25:05 -0000
- Subject: [Bug fortran/35707] Search /usr/local/include and /usr/include for .mod files
- References: <bug-35707-13404@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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-(...) enough to tell that it is 64 bits (besides /usr/lib64)
?
My opinion is that the proper way to distribute fortran so-called "headers" is
via interfaces in fortran files, not via modules.
If we add a "standard" place for fortran modules, everybody will use it, and it
will raise countless problems (need to provide several modules versions for
different compiler versions, doesn't work if the compiler is upgraded, ...)
In short, I agree with FX. :)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707