public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: Lou Umscheid <umscheid@verizon.net>, cygwin@cygwin.com
Subject: Re: Fortran Installation
Date: Sun, 3 Jan 2021 14:03:04 -0700	[thread overview]
Message-ID: <f2f58d9a-0d84-a9a1-595f-93a39fde307a@Shaw.ca> (raw)
In-Reply-To: <865ad6b0-4329-42ac-54a2-50bb8d4a7122@verizon.net>

On 2021-01-03 12:18, Lou Umscheid via Cygwin wrote:
> On 1/3/2021 1:41 PM, Brian Inglis wrote:
>> On 2021-01-03 11:37, Brian Inglis wrote:
>>> On 2021-01-03 11:22, Lou Umscheid via Cygwin wrote:
>>>> On 1/3/2021 12:28 PM, Brian Inglis wrote:
>>>>> On 2021-01-03 09:44, Lou Umscheid via Cygwin wrote:
>>>>>> I would like to install Fortran on newly installed Cygwin64 on my new LG 
>>>>>> laptop. I did this 9+ years ago for Cygwin32 on my Dell T1600 which is now 
>>>>>> fading. The process 9 years ago was long and hard over several weeks with 
>>>>>> many fallbacks and redo's. I am competent in Fortran programming but have 
>>>>>> only a minimum knowledge of Linux/Unix. Can anyone point me to a guide (I 
>>>>>> searched but could not find any) to installing Fortran, including which 
>>>>>> files to download, PATH, alias changes, etc. I know it is a lot to ask, 
>>>>>> but ANY help would be appreciated.
>>>>>
>>>>> To get a list of manually picked and installed packages in your current 
>>>>> Cygwin installation (excluding library packages except if they are devel or 
>>>>> doc packages) run the following command against your current installation:
>>>>>
>>>>> $ awk '$3 && ($1 !~ /^lib/ || $1 ~ /-(devel|doc)/) {print $1}' \
>>>>>     /etc/setup/installed.db | tee cygwin-packages-picked.txt
>>>>>
>>>>> * transfer the file cygwin-packages-picked.txt to your new system e.g. your 
>>>>> Windows account Downloads folder on your new system,
>>>>> * download https://cygwin.com/setup-x86_64.exe to e.g. your Windows account 
>>>>> Downloads folder on your new system,
>>>>> * run setup-x86_64 on your new system with no selections to install a basic 
>>>>> Cygwin installation for you, then
>>>>> * start a Cygwin shell in a terminal session, and
>>>>> * rerun the Cygwin setup program with e.g.:
>>>>>
>>>>> $ cygstart /proc/cygdrive/c/Users/.../Downloads/setup-x86_64 \
>>>>> -P "`cat /proc/cygdrive/c/Users/.../Downloads/cygwin-packages-picked.txt`"
>>>>>
>>>>> to start installing the manually picked packages you had on your old system 
>>>>> (dependencies will be automatically pulled in):
>>>>> * you *MUST* exit your Cygwin shell and terminal, and ensure that you have 
>>>>> no other Cygwin processes still running, before allowing the Cygwin setup 
>>>>> program to proceed; and
>>>>> * wait patiently for all the package downloads, installations, and 
>>>>> post-install scripts to run to completion, before trying to do anything 
>>>>> more under Cygwin on your new system.
>>>
>>>> wow; thanks for quick response. I tried running your first command but got
>>>> the message:
>>>>
>>>> awk: fatal: cannot open file ' /etc/setup/installed.db' for reading (No such 
>>>> file or directory) >
>>>> The file seems to be there and I checked my input so I do not know what when 
>>>> wrong. Any suggestions?

>>> File name shown is ' /etc/setup/installed.db' - includes a leading space - do 
>>> not use any quotes or add spaces in file names - or just paste the second 
>>> line at the end of the first line, with an (unquoted) space between if required.
>>
>> ...and remove any \ continuation escape if you paste the lines together - that 
>> may well have been your issue!
> Another question, if I may: does your procedure install both Fortran and
> Dislin which are installed on the T1600? I do not see them in 
> cygwin-packages-picked.txt.

The Cygwin Fortran package is gcc-fortran (gfortran/f95 symlink): you should see 
this unless you have been using a proprietary closed source compiler.
It looks like Dislin is a proprietary closed source plotting package which you 
will have to find, acquire, install, and configure separately, or migrate 
settings from your old system.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-01-03 21:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b3d295a7-b7d9-9b33-0391-cc33bb39c029.ref@verizon.net>
2021-01-03 16:44 ` Lou Umscheid
2021-01-03 17:11   ` Marco Atzeri
2021-01-04  0:19     ` Lou Umscheid
2021-01-04  8:42       ` Marco Atzeri
2021-01-05 14:18         ` Lou Umscheid
2021-01-03 17:20   ` Achim Gratz
2021-01-03 17:28   ` Brian Inglis
2021-01-03 18:22     ` Lou Umscheid
2021-01-03 18:27       ` Achim Gratz
2021-01-03 18:37       ` Brian Inglis
2021-01-03 18:41         ` Brian Inglis
2021-01-03 18:58           ` Lou Umscheid
2021-01-03 19:18           ` Lou Umscheid
2021-01-03 21:03             ` Brian Inglis [this message]
2021-01-03 21:42               ` Lou Umscheid
2021-01-03 22:59                 ` Brian Inglis
2021-01-04  0:29               ` Lou Umscheid
2021-01-04  6:04                 ` Brian Inglis
2021-01-04  6:48               ` David Billinghurst

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=f2f58d9a-0d84-a9a1-595f-93a39fde307a@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --cc=cygwin@cygwin.com \
    --cc=umscheid@verizon.net \
    /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).