DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=RQOU1KlxcH7jkk65
	WZe4lAJ88pIxjQRLhWGWU4O1roquIu8cDaUZ6L/NCS9Qgvgd/noHEcYqA3JItEOM
	6lXq8z+BcaFZsWs52haxdzdQ2VtzEwkJy2l5SFzkNUtztmEXhjm30+F6CUjlxk0w
	IH7OQjPicf4Ho8uYpy1eGnWdK0s=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 28 Oct 2019 20:17:03 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <1567900977.20191028201703@yandex.ru>
To: William John <wj552 AT nyu DOT edu>, cygwin AT cygwin DOT com
Subject: Re: OPENMPI only works on Cygwin Terminal not windows Command Line
In-Reply-To: <CAK=LkowuGPCG-OEg8Sfo-kwr07xQBGVWj6fvjv9ueFTV-Umn_g@mail.gmail.com>
References: <CAK=LkowuGPCG-OEg8Sfo-kwr07xQBGVWj6fvjv9ueFTV-Umn_g AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, William John!

> 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.

Cygwin may use extension-less names to call programs. Something CMD can not do
without being explicitly told to.
If that's your case, you can still make symlinks to .exe'cutable names to make
them recognizable by native tools. I would suggest $HOME/bin or /usr/local/bin
for such custom symlinks.

> 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?

There are two available solutions.
One is to stick to one ecosystem. If you want to use Cygwin-provided programs,
stick to Cygwin environment. It's much more obvious, although sometimes
daunting if you want to frequently use wide array of native console
applications.
Another solution is to setup your system to use Cygwin programs
transparently. It requires much care and understanding of both Cygwin and
Windows, and generally not advised to people without certain experience in
both.


-- 
With best regards,
Andrey Repin
Monday, October 28, 2019 20:11:55

Sorry for my terrible english...


--
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