public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lawrence Bernardo <loric.bernardo@gmail.com>
To: moss@cs.umass.edu
Cc: cygwin@cygwin.com
Subject: Re: Setting up a proper modelling environment in Cygwin
Date: Mon, 14 Sep 2020 11:00:22 +0900	[thread overview]
Message-ID: <CAOt=qgkdm-Uebzr70HjXcNP59Tk+nFjNBjAGwVgsDJUBRBvA6w@mail.gmail.com> (raw)
In-Reply-To: <7ea73c16-538d-5f53-dce9-95dc41be0778@cs.umass.edu>

Dear Eliot,

Thank you for your response. Indeed, after trying a number of different
combinations of component versions using the setup application, I found a
working set based on gcc/gfortran version 7.4.0. And I get what you mean
about Cygwin-specifc adjustments, as one of the codes I tried to compile
didn't succeed, and after a google search, found that it was mainly a
Cygwin issue. Thankfully, someone was already able to find a fix.

The cygwin time machine sounds interesting too, for the case of some really
old codes that might need to be dug up and reused. But thank you again for
your reply, it has been really helpful.

Best,
Lawrence


On Fri, Sep 11, 2020 at 10:33 PM Eliot Moss <moss@cs.umass.edu> wrote:

> On 9/10/2020 10:37 PM, 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.
>
> Not sure if anyone has responded yet ...
>
> You can:
>
> - Install the specific version of gfortran (gcc suite) that you need.
> - Build the other things from sources in Cygwin, using the source packages.
>
> There might be rough edges if there are cygwin-specific adjustments that
> have been
> made and they don't quite match the version you want.
>
> There is also the cygwin time machine that you can use to get any old
> versions.
> (I've not used it, but know it exists and sometimes helps folks with
> situations
> like this.)
>
> Regards - Eliot Moss
>

  reply	other threads:[~2020-09-14  2:00 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 [this message]
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
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=qgkdm-Uebzr70HjXcNP59Tk+nFjNBjAGwVgsDJUBRBvA6w@mail.gmail.com' \
    --to=loric.bernardo@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=moss@cs.umass.edu \
    /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).