Hello Patrice, This list is being to be deprecated, please ask on fedora-devel-list@xxxxxxxxxxx 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 my first question is what is your advice about fortran modules > directories? > > My second is, in case it is meaningful, what about my proposal regarding > rpm macros? > > -- > Pat > > -- > Fedora-packaging mailing list > Fedora-packaging@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-packaging -- Marek Mahut http://www.fedoraproject.org/ Fedora Project http://www.jamendo.com/ -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
