From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Setting up a proper modelling environment in Cygwin
Date: Sat, 12 Sep 2020 08:51:50 +0200 [thread overview]
Message-ID: <f703e53e-403d-e2de-7844-c4f8f72f40cd@gmail.com> (raw)
In-Reply-To: <22263d73-bd15-3558-bdfe-7cc960db5f65@SystematicSw.ab.ca>
On 12.09.2020 07:39, Brian Inglis wrote:
> On 2020-09-11 08:59, Marco Atzeri via Cygwin 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:
>
>>> - netcdf-fortran
>
>>> 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.
>
>> netcdf-fortran needs a rebuild
>>
>> $ zcat /usr/include/netcdf.mod | head -n 1
>> GFORTRAN module version '14' created from netcdf4.f90
>
> Worse, setup.ini somehow now contains component package netcdf-fortran-debuginfo
> but not netcdf-fortran itself!
>
of course they are called a bit differently
libnetcdf-fortran-devel 4.5.2-1
libnetcdf-fortran_7 4.5.2-1
next prev parent reply other threads:[~2020-09-12 6:51 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 [this message]
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=f703e53e-403d-e2de-7844-c4f8f72f40cd@gmail.com \
--to=marco.atzeri@gmail.com \
--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).