Ralf Corsepius wrote:
On Sun, 2007-10-21 at 14:23 -0400, Tom "spot" Callaway wrote:
On Sun, 2007-10-21 at 19:55 +0200, Patrice Dumas wrote:
On Sun, Oct 21, 2007 at 10:18:42AM -0400, Tom spot Callaway wrote:
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?)
Yes, I chose f90 because it was the oldest fortran standard version with
these .mod. To be more genereic, maybe
%_includedir/%_lib/fortran
This seems reasonable to me. Anyone else?
I think we will need some gcc's f90 specialist's opinion.
My gut feeling is, a manually multilib'ed include directory like the one
above (%_includedir/%_lib) can't be right, unless GCC starts to support
searching multilib'ed include dirs (It currently doesn't).
That said, I am in favor of a directory rooted at %{_libdir}, say
%{_libdir}/finclude
or %{_libdir}/f90
or %{_libdir}/gfortran
We have precedent (on a smaller scale) for this from the C world as well
with things like %{_libdir}/glib-2.0/include/glibconfig.h.
After reading that these mod files are potentially compiler dependent as
well, using %{_libdir}/f90 and %{_libdir}/gfortran makes a lot of sense
to me.
-Toshio
--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging
