public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lawrence Bernardo <loric.bernardo@gmail.com>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Setting up a proper modelling environment in Cygwin
Date: Mon, 14 Sep 2020 11:07:38 +0900	[thread overview]
Message-ID: <CAOt=qgnk08D=HpJH+p4ztsF9-rjZSm2A2e02q8+gXooCbp7r-Q@mail.gmail.com> (raw)
In-Reply-To: <90d505d5-11fc-418d-02e4-73dd423a92ce@gmail.com>

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

On Fri, Sep 11, 2020 at 11:59 PM Marco Atzeri via Cygwin <cygwin@cygwin.com>
wrote:

> On 11.09.2020 04:37, Lawrence Bernardo via Cygwin wrote:
> > Dear Cygwin users and developers,
> >
> > I am trying to run some models based on the ROMS ocean modeling system.
> And
> > although I mainly run such models on Linux supercomputing systems, I
> > sometimes use Cygwin to make test runs. However, whenever I install
> Cygwin
> > on a new PC, I often find that my set up on an older PC I had been using
> > doesn't work properly. After looking deeper into the issues, it seems
> that
> > proper compilation requires that the same fortran compiler (gfortran in
> > this case) be used to compile the necessary components.
> >
> > And as far as I understand, these components would mainly be:
> > - zlib
> > - hdf5
> > - netcdf
> > - netcdf-fortran
> > - openmpi
> >
> > As the gfortran compiler version number used for these different
> components
> > is not indicated whenever I run cygwin setup-x86_64.exe, I am left to
> guess
> > which version numbers for each to select. Of course, another option would
> > be to accept the defaults for some components, and then compile my own
> > version of say, netcdf, but this attempt almost always fails, and I'm not
> > sure if this is due to conflicts with the already existing cygwin setup.
> >
> > Given the issues above, would anyone have any suggestions or
> > recommendations on how to best achieve the setup I would like to have? I
> > will greatly appreciate any help.
> >
> > Best regards,
> > Lawrence
> > --
>
>
> for what I am aware the problem is only present with
> fortran modules if you are using them.
> C interface are not involved
>
> zlib should not be involved as it has no fortran specific modules
> same for hdf5.
>
> 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
>
> netcdf-fortran needs a rebuild
>
> $ zcat /usr/include/netcdf.mod | head -n 1
> GFORTRAN module version '14' created from netcdf4.f90
>
> Give me some days for an update of the package
> And I will need to re-build for test gcc 10 also,
> but it is less urgent
>
>
> Regards
> Marco
>
>
>
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>

  parent reply	other threads:[~2020-09-14  2:07 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 [this message]
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='CAOt=qgnk08D=HpJH+p4ztsF9-rjZSm2A2e02q8+gXooCbp7r-Q@mail.gmail.com' \
    --to=loric.bernardo@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@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).