Your message dated Tue, 1 Sep 2020 12:42:57 +0200
with message-id <[email protected]>
and subject line Re: Bug#922688: findent: Please drop build-depend on gfortran
has caused the Debian Bug report #922688,
regarding findent: Please drop build-depend on gfortran
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
922688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922688
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: findent
Version: 2.8.2-1
Severity: minor
Dear Maintainer,
I'm rebuilding Debian with flang, as a Secondary Fortran compiler. In the
process of this, I see that your package 'findent'
build depends on gfortran. It doesn't need to, as it doesn't use gfortran to
build.
You could use "Recommends: gfortran | fortran-compiler" for the package itself,
to depend on a Fortran compiler at runtime.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_IE.UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) (ignored: LC_ALL set to
en_IE.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages findent depends on:
ii libc6 2.28-7
ii libgcc1 1:8.2.0-21
ii libstdc++6 8.2.0-21
findent recommends no packages.
findent suggests no packages.
--- End Message ---
--- Begin Message ---
Closing this bug.
On Tue, 19 Feb 2019 16:36:22 +0100 Willem Vermin <[email protected]> wrote:
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
--- End Message ---
