http://www.fedoraproject.org/wiki/Packaging:Fortran states:
As Fortran modules are architecture and GCC version specific, they MUST be placed into %{_fmoddir} (or its package-specific subfolder in case the modules have generic names), which is owned by 'gcc-gfortran'. For directory ownership any packages containing Fortran modules MUST Requires: gcc-gfortran%{_isa}.
I did this in netcdf, and ended up with:
The following packages in the repository suffer from broken dependencies:
====================================================================== The results in this summary consider Test Updates! ======================================================================
package: netcdf-devel-4.0.1-2.fc11.i586 from fedora-updates-testing-11-x86_64 unresolved deps: gcc-gfortran(x86-32)
package: netcdf-devel-4.0.1-2.fc11.ppc64 from fedora-updates-testing-11-ppc unresolved deps: gcc-gfortran(ppc-64)
because gcc-gfortran (like gcc) is apparently not multi-lib.
So, what to do?
On Wed, 2009-11-04 at 13:53 -0700, Orion Poplawski wrote:
http://www.fedoraproject.org/wiki/Packaging:Fortran states:
As Fortran modules are architecture and GCC version specific, they MUST be placed into %{_fmoddir} (or its package-specific subfolder in case the modules have generic names), which is owned by 'gcc-gfortran'. For directory ownership any packages containing Fortran modules MUST Requires: gcc-gfortran%{_isa}.
I did this in netcdf, and ended up with:
Thanks for the report.
The %{_fmoddir} ownership issue https://bugzilla.redhat.com/show_bug.cgi?id=513985 still isn't resolved due to inactivity (read: total silence) of the gcc maintainers.
In the meantime I recommend just commenting out the Requires: gcc-gfortran%{_isa} line.
**
Since 64-bit gcc is built to be able to compile in 32-bit mode, it would be logical to make the x86_64 gfortran own the 32-bit %{_fmoddir} and Provides: gfortran(x86-32) (and the same thing on other arches, too).
This has to be discussed with the gcc maintainers, though.
packaging@lists.fedoraproject.org