From Fedora Project Wiki
(Merge Fortran Guidelines -- note that Jussi needs to implement the package updates) |
No edit summary |
||
| Line 18: | Line 18: | ||
* If it is decided to keep using an unversioned, multilib compatible <code>%{_fmoddir}</code>, the ''gcc-gfortran'' package must be changed to own <code>%{_fmoddir}</code> and all package containing modules must <code>Requires: gcc-gfortran</code>. | * If it is decided to keep using an unversioned, multilib compatible <code>%{_fmoddir}</code>, the ''gcc-gfortran'' package must be changed to own <code>%{_fmoddir}</code> and all package containing modules must <code>Requires: gcc-gfortran</code>. | ||
* If it is decided to use a GCC-versioned <code>%{_fmoddir}</code>, the preexisting <code>%{_fmoddir}</code> macro in <code>redhat-rpm-macros</code> must be changed from <code>%{_libdir}/gfortran/modules</code> to <code>/usr/lib/gcc/<target>/<version>/finclude</code> which is already used and owned by gfortran. After that a mass rebuild of all packages containing Fortran modules must be performed. | * If it is decided to use a GCC-versioned <code>%{_fmoddir}</code>, the preexisting <code>%{_fmoddir}</code> macro in <code>redhat-rpm-macros</code> must be changed from <code>%{_libdir}/gfortran/modules</code> to <code>/usr/lib/gcc/<target>/<version>/finclude</code> which is already used and owned by gfortran. After that a mass rebuild of all packages containing Fortran modules must be performed. | ||
Latest revision as of 20:18, 15 September 2009
Modules and include files
This has been merged. See Packaging:Fortran
Packaging of Fortran programs
This has been merged. See Packaging:Fortran
Required changes
Needs to be done
This portion is not guideline material. Jussi, can you take care of this?
This portion is not guideline material. Jussi, can you take care of this?
Packages that contain modules in the wrong place must be found and fixed (e.g. find all packages that BR: gcc-gfortran and contain '.mod' files).
The module files depend on the used compiler version and the architecture. The versioning should not matter, as mass rebuilds are done anyway whenever GCC is updated to a newer version. It is important, however, if there are multiple Fortran compilers present on the system.
- If it is decided to keep using an unversioned, multilib compatible
%{_fmoddir}, the gcc-gfortran package must be changed to own%{_fmoddir}and all package containing modules mustRequires: gcc-gfortran. - If it is decided to use a GCC-versioned
%{_fmoddir}, the preexisting%{_fmoddir}macro inredhat-rpm-macrosmust be changed from%{_libdir}/gfortran/modulesto/usr/lib/gcc/<target>/<version>/fincludewhich is already used and owned by gfortran. After that a mass rebuild of all packages containing Fortran modules must be performed.