public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: tprince@intelretiree.com, cygwin@cygwin.com
Cc: Tim Prince <tcprince@live.com>
Subject: Re: Problem about installing PGI on Cygwin
Date: Thu, 2 Apr 2020 18:25:48 -0400	[thread overview]
Message-ID: <c58cd782-0884-8c86-fb85-5263678f48bf@cs.umass.edu> (raw)
In-Reply-To: <YTOPR0101MB1804B9FD71625FD2363E3A5BB7C60@YTOPR0101MB1804.CANPRD01.PROD.OUTLOOK.COM>

On 4/2/2020 10:48 AM, Tim Prince via Cygwin wrote:
> On 4/2/2020 9:14 AM, Andrew Schulman via Cygwin wrote:
>>> I tried to install PGI (Linux version) on Cygwin, however, Cygwin told me that PGI can only be installed under Linux operator system. So is there any method to install PGI on Cygwin?
>>
>> What is PGI? Where do you get it?
>>
>> --
> 
> Cygwin never aimed to be a binary compatible linux emulator.  I have run
> the PGI for windows  Of course, Visual Studio compatible tools aren't
> link compatible with any cygwin tools, other than possibly, if not
> depending on run time library compatibility, the mingw ones.  A few
> years ago, Lahey attempted to market commercial support for gfortran
> under cygwin, but I don't think it was successful, beyond implementing
> some important improvements in gfortran.

Agreed.  The usual advice: If PGI has source, there is a reasonable chance
it can be built under Cygwin unless it uses unusual OS features.

Other handy options include the Windows Subsystem for Linux (WSL), which is
still part of the Windows Insider Program, but is apparently moving toward
being a more standard Windows component, and of course virtual machines
such as VMWare or VirtualBox.

Some things may build with mingw, which (loosely speaking) is a suite of
Linux-like tools for building native Windows applications.

I'm sure others here can elaborate!

Regards - Eliot Moss


      reply	other threads:[~2020-04-02 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 13:06 981800529
2020-04-02 13:14 ` Andrew Schulman
2020-04-02 14:48   ` Tim Prince
2020-04-02 22:25     ` Eliot Moss [this message]

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=c58cd782-0884-8c86-fb85-5263678f48bf@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    --cc=tcprince@live.com \
    --cc=tprince@intelretiree.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).