[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#714730: gfortran: handling binNMU for .mod file format change



Am 24.03.2014 18:46, schrieb Sébastien Villemot:
> Le mercredi 12 mars 2014 à 18:44 +0100, Sébastien Villemot a écrit :
> 
>> More specifically, I think that dh_fortran_mod should do the following:
>> 
>> - it would read a file debian/[package.]fortran-mod, which would contain 
>> a list of mod files created by gfortran and to be installed into binary 
>> packages
>> 
>> - for each of these mod files, it would determine the mod version by 
>> inspecting the contents, and then install the file into
>> /usr/include/fortran/gcc-<version>/<multiarch-triplet>/. This is the
>> proposed standard location, see 
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49138
>> 
>> - it would also add the relevant virtual dependencies on 
>> gfortran-mod-<version> in ${misc:Depends}
> 
> I have implemented this. The code is on alioth:
> 
> http://anonscm.debian.org/gitweb/?p=debian-science/packages/dh-fortran-mod.git;a=tree
>
> 
git://anonscm.debian.org/debian-science/packages/dh-fortran-mod.git
> 
> doko: does that sound like a reasonable plan to you? In particular, are you
> willing to incorporate a patch to gfortran to implement the standard 
> include location?

so are the mod files always architecture dependent? If not then maybe we
should have two directories.

>> into /usr/include/fortran/gcc-<version>/<multiarch-triplet>/. This is

we have to change this one to use a location in

  /usr/include/<multiarch-triplet>/

like we do for c++, to find the correct files for foreign architectures.

do we really need the gcc- prefix?  this doesn't seem to be orthogonal to the
c++ case.

if possible, please test such a patch with a cross compiler too.

So we should have

  /usr/include/<multiarch-triplet>/fortran/<version>

and if needed

  /usr/include/fortran/<version>

Matthias


Reply to: