Yes, I see it now, I arranged that gfortran is not needed when building.
Probably it is best to remove the dependency altogether. When developing
on a system with gfortran, the compile checks will automatically be done.
Adapting to another fortran compiler would require the conversion of the
compile flags also.
So, what is the best way to go? I plan to release the next version
(3.x.y) within a month or so, it has been stable for several months now.
In that version I will remove the dependency. Is that soon enough for you?
Willem
On 2/19/19 3:31 PM, Alastair McKinstry wrote:
Dear Willem,
Build-depend on "gfortran | fortran-compiler".
This will make it work with flang, if that is present instead of gfortran.
Looking at the program, it compiles fine without gfortran, and 'make
check' succeeds !
set -x in test-compile.sh reveals:
+ echo ../test-compile.sh: ../progfixed-dos.f
../test-compile.sh: ../progfixed-dos.f
+ gfortran=gfortran
+ gfortran -v
+ echo Cannot compile: gfortran not installed
Cannot compile: gfortran not installed
+ gfortran=:
+ rc=0
It hard-codes gfortran.
If 'fortran-compiler' is included (either gfortran or flang), then the
alternatives binaries /usr/bin/f77 and /usr/bin/f95 are set.
The code should use $FC or $F77 if they are set, failing that the f77,
f95 binaries; so:
fortran=${F77:-f77}
or
fortran=${FC:-f95}
as appropriate in the tests.
Best regards
Alastair
On 19/02/2019 13:58, Willem Vermin wrote:
Dear Alastair,
findent uses gfortran when running 'make check', to confirm that
indented sources are still compilable.
If you know how to specify a general fortran compiler in stead of
specific gfortran, just let me know and I can take care of that in the
next release of findent, or, if that is possible, in the current
version of findent.
