public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: Lawrence Bernardo <loric.bernardo@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Setting up a proper modelling environment in Cygwin
Date: Mon, 14 Sep 2020 20:25:52 +0200	[thread overview]
Message-ID: <a4613821-a4de-ef7f-a804-1b225cb17605@gmail.com> (raw)
In-Reply-To: <CAOt=qgnk08D=HpJH+p4ztsF9-rjZSm2A2e02q8+gXooCbp7r-Q@mail.gmail.com>

On 14.09.2020 04:07, Lawrence Bernardo wrote:
> Thank you Marco for addressing my concerns. And I think checking for the 
> fortran module consistency will be really helpful for me to assess 
> issues I run into in the future. I have rolled back the versions I have 
> been using to all be based on gfortran/gcc version 7.4.0, but an update, 
> although not urgent for now, would indeed be helpful. Lately, some 
> other codes I've been running have been having problems with this older 
> version, so I'll stay tuned for your updates to the package.
> 
> Best regards,
> Lawrence
> 

bottom post on this mailing list, please.

The netcdf-fortran is already aligned

https://sourceware.org/pipermail/cygwin-announce/2020-September/009700.html

  $ zcat /usr/include/netcdf.mod | head -n 1
GFORTRAN module version '15' created from netcdf4.f90

Regards
Marco


  reply	other threads:[~2020-09-14 18:25 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
2020-09-14  2:07   ` Lawrence Bernardo
2020-09-14 18:25     ` Marco Atzeri [this message]
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=a4613821-a4de-ef7f-a804-1b225cb17605@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=loric.bernardo@gmail.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).