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: "dfranke 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 12:50:38 -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 #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 support files and could be
placed/distributed in a project's $libdir?! If there's a difference between
32-bit and 64-bit .mod-files, placing them in their respective $multilibdir
would solve this.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707