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

Bug#948033: Fwd: Bug#948033: lintian: Fortran test fails on 'flang' mod files



Copying bug for the record.

On Sat, Jan 4, 2020 at 12:39 AM Alastair McKinstry <mckinstry@debian.org> wrote:
>
> On 03/01/2020 20:05, Felix Lechner wrote:
> >
> > On Fri, Jan 3, 2020 at 6:33 AM Alastair McKinstry <mckinstry@debian.org> wrote:
> >> I'm adding support for the flang fortran compiler , which ships mod files that are in a different format.
> > Where is the format specified? An online search was unsuccessful.
> >
> I don't know of any. Its an internal format originally from PGI (similar
> to that used in the PGI Fortran compiler.
>
> There are no formal standards for these.
>
> >> New lintian tests should be added
> > To differentiate, we call them checks. (Tests are in our test suite.)
> > Which checks would you like to see for flang, please?
> >
> >> flang mod files should be found in $LIBDIR/fortran/flang-$(version)
> > Are flang's files architecture-independent? By comparison, gfortran's
> > modules ship in /usr/lib/gcc//usr/lib/gcc/x86_64-linux-gnu/8/finclude/
> > /finclude/ (for
> > gfortran-8).
>
> Thats the location of module files that ship with  gfortran. Module
> files can typically be anywhere in the include path (for any fortran
> compiler).
>
> I am writing a Fortran policy to place them in
> /usr/lib/gcc/x86_64-linux-gnu/fortran/$compiler
>
> where compiler is set by compiler version, currently gfortran-mod-8 or
> flang-mod-34.
>
> Adding patches to gfortran and flang to look in those directories (and
> subdirectories) first, and have a debhelper command dh-fortran-mod to
> place  mod files in these directories.
>
> Kind regards
>
> Alastair McKinstry, <alastair@sceal.ie>, <mckinstry@debian.org>, https://diaspora.sceal.ie/u/amckinstry
> Misentropy: doubting that the Universe is becoming more disordered.


Reply to: