From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Setting up a proper modelling environment in Cygwin
Date: Sat, 12 Sep 2020 11:29:57 +0200 [thread overview]
Message-ID: <87tuw3wdey.fsf@Rainer.invalid> (raw)
In-Reply-To: <90d505d5-11fc-418d-02e4-73dd423a92ce@gmail.com> (Marco Atzeri via Cygwin's message of "Fri, 11 Sep 2020 16:59:24 +0200")
Marco Atzeri via Cygwin writes:
> On 11.09.2020 04:37, Lawrence Bernardo via Cygwin wrote:
> for what I am aware the problem is only present with
> fortran modules if you are using them.
> Now the current gfortran has
>
> $ zcat
> /usr/lib/gcc/x86_64-pc-cygwin/9.3.0/finclude/ieee_arithmetic.mod|head
> -n 1
> GFORTRAN module version '15' created from ieee_arithmetic.F90
>
> openmpi was built with last gcc so it is aligned
>
> $ zcat /usr/lib/mpi.mod |head -n 1
> GFORTRAN module version '15' created from mpi-ignore-tkr.F90
If these are dependent on the compiler version / module ABI version,
then they should be moved to some version dependent directory, then. I
have no idea yet how to name that. The Linux distributions I've looked
at have a very complicated folder structure that caters to the HPC folks
that want multiple parallel installed versions.
With gcc10 the gfortran package will provide "gfm15" and that number
will be incremented in lockstep with the Fortran module version so that
setup can figure out if things match. In order for this to work any
packages delivering Fortran modules would need to have a manual require
on that.
> netcdf-fortran needs a rebuild
>
> $ zcat /usr/include/netcdf.mod | head -n 1
> GFORTRAN module version '14' created from netcdf4.f90
Certainly none of these files should live in /usr/include.
These seem to be the only two packages in the distribution that provide
Fortran modules, so the impact is currently limited.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2020-09-12 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 2:37 Lawrence Bernardo
2020-09-11 13:33 ` Eliot Moss
2020-09-14 2:00 ` Lawrence Bernardo
2020-09-11 14:59 ` Marco Atzeri
2020-09-12 5:39 ` Brian Inglis
2020-09-12 6:51 ` Marco Atzeri
2020-09-12 6:13 ` ASSI
2020-09-12 6:56 ` Marco Atzeri
2020-09-12 8:47 ` Achim Gratz
2020-09-12 10:24 ` Marco Atzeri
2020-09-12 9:29 ` Achim Gratz [this message]
2020-09-14 2:07 ` Lawrence Bernardo
2020-09-14 18:25 ` Marco Atzeri
2020-09-15 0:23 ` Lawrence Bernardo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuw3wdey.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).