[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Fedora-packaging] fortran .mod files



On Tue, 23 Oct 2007 13:46:40 +0200 Ralf Corsepius wrote:
> On Tue, 2007-10-23 at 07:19 -0400, Jakub Jelinek wrote:
> 
> > But I guess I'll need to make some changes, because say on
> > i386 this is /usr/lib/gcc/i386-redhat-linux/4.1.2/finclude,
> > while on x86_64 for 32-bit rpms
> > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/finclude/ )
> What I was referring to (and implicitly proposing) was GCC/gfortran to
> be extended to have a "standard, system-wide, GCC-independent" *.mod
> installation directory/*.mod-search path, similar to /usr/include for
> cpp'ed sources (c/c++-headers).
> 
> But ... if, as you say, *.mod's are really are compiler-dependent,
> then gcc-gfortran(f90) has a real problem.


Yes, the F90/F95/F2003 *.mod files are compiler- and target-specific.
As FX Coudert (one of the gfortran developers) pointed out:

  http://gcc.gnu.org/ml/fortran/2007-10/msg00306.html

it may be best to treat the *.mod files more like libraries (and less
like headers).  FX's recommendation was:

  /usr/lib*/finclude or /usr/finclude* where * can be 32, 64 or nothing

which is quite similar to Spot's "I like this the best so far" comment
regarding the location:

   %{_libdir}/gfortran/modules

So are we reaching a consensus here on "%{_libdir}/gfortran/modules"?
Does anyone have any technical objections to it?

Ed


-- 
Edward H. Hill III, PhD  |  ed eh3 com  |  http://eh3.com/

Attachment: signature.asc
Description: PGP signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]