From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: OPENMPI only works on Cygwin Terminal not windows Command Line
Date: Sun, 27 Oct 2019 20:04:00 -0000 [thread overview]
Message-ID: <b060cbdb-c3e9-e08d-eba2-763e5fc97d88@SystematicSw.ab.ca> (raw)
In-Reply-To: <bb6c2e33-d5e6-08a0-0354-5ba2a8815373@towo.net>
On 2019-10-27 13:21, Thomas Wolff wrote:
> Am 27.10.2019 um 19:56 schrieb William John:
>> On Sat, Oct 26, 2019 at 11:33 PM William John <wj552@nyu.edu> wrote:
>>> I recently installed openmpi and libopenmpi-devel on my windows machine.
>>> However, I cannot call mpicc on my windows cmd, rather I get "'mpicc' is
>>> not recognized as an internal or external command, operable program or
>>> batch file". This is weird because I have added C:\cygwin64\bin
>>> and C:\cygwin64 to my System variables. The command mpicc --version also
>>> works on my cygwin terminal so I am kind of confused here as to what to do
>>> with the set up. I checked the bin inside cygwin64 and I found mpicc and
>>> mpiexec, I am just confused as to what is going on with the configuration
>>> for my windows command line. Would it be possible to direct me to a
>>> solution or to help me with this?
>> I did add it to the Path and also restarted the computer and the command
>> line. I do see that the file mpicc is a symbolic link to opalwrapper
>> executable file and windows cannot recognize that. Is there some way to
>> remedy this?
> Change the soft link to a hard link, in cygwin, with an exe suffix.
Cygwin needs to be running Windows 10 in dev mode with WSL installed to enable
this without elevation I think.
Otherwise you will need an elevated shell, and be careful if you use mklink, as
the arguments are swapped from ln:
> REM mklink /h LINK_NAME TARGET
> mklink /h C:\cygwin64\bin\mpicc.exe C:\cygwin64\bin\opalwrapper.exe
> mklink /h C:\cygwin64\bin\mpiexec.exe C:\cygwin64\bin\opalwrapper.exe
> And you really don't need to restart Windows after changing an environment
> variable.
Just close and reopen any cmd or other shell processes, including Windows File
Explorer, if necessary for Windows Shell Extensions, from Task Manager/Processes
tab/Windows Explorer/menu Restart.
> Also, please don't "top-post" here.
Show *AND* Tell ;^>
--
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.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-10-27 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 3:33 William John
2019-10-27 7:06 ` john doe
2019-10-27 8:48 ` Thomas Wolff
2019-10-27 15:59 ` Hans-Bernhard Bröker
2019-10-27 18:56 ` William John
2019-10-27 19:21 ` Thomas Wolff
2019-10-27 20:04 ` Brian Inglis [this message]
2019-10-28 4:59 ` Hard links [was: Re: OPENMPI only works on Cygwin Terminal not windows Command Line] Thomas Wolff
2019-10-28 17:35 ` OPENMPI only works on Cygwin Terminal not windows Command Line Andrey Repin
2019-10-28 17:20 ` Andrey Repin
2019-10-27 21:25 William John
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=b060cbdb-c3e9-e08d-eba2-763e5fc97d88@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).