From: William John <wj552@nyu.edu>
To: cygwin@cygwin.com
Subject: OPENMPI only works on Cygwin Terminal not windows Command Line
Date: Sun, 27 Oct 2019 03:33:00 -0000 [thread overview]
Message-ID: <CAK=LkowuGPCG-OEg8Sfo-kwr07xQBGVWj6fvjv9ueFTV-Umn_g@mail.gmail.com> (raw)
Dear Cygwin,
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?
Best,
William John
--
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 reply other threads:[~2019-10-27 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 3:33 William John [this message]
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
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='CAK=LkowuGPCG-OEg8Sfo-kwr07xQBGVWj6fvjv9ueFTV-Umn_g@mail.gmail.com' \
--to=wj552@nyu.edu \
--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).