On Sun, 2007-10-21 at 00:24 +0200, Patrice Dumas wrote: > Hello, > > Currently there is no guideline regarding fortran 90 .mod, it seems to > me that one is needed. These files are generated by gfortran when > building a module. These are text files, but not intended to be read by > humans. They are architecture dependent. When compiling some code that > uses the module, the .mod has to be found in the include path (for > example in a directory specified by -I). > > Where should the .mod be installed? I propose > > %_libdir > %_libdir/include > %_libdir/modules > %_libdir/mod > %_libdir/f90 > %_includedir/%_lib > %_includedir/%_lib/modules > %_includedir/%_lib/mod > %_includedir/%_lib/f90 > > (f90 may also be replaced by another meaningfull subdirectory name). > > This directory could be called %_fmoddir > > And add -I%_fmoddir in FFLAGS when compiling some code that > requires the module. > > > The optimal situation would be to have %_fmoddir defined in rpm macros > and -I%_fmoddir added to default FFLAGS. So, I think that if they're searched in the include path, they should be under the %_includedir. Modules/mod is too vague, but perhaps f90 is too specific? Wouldn't later fortran modules hit this as well? (f95? 2003?) I'm also not opposed to making this a macro, it seems logical to me. ~spot -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
