From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69955 invoked by alias); 27 Oct 2019 20:04:40 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 69946 invoked by uid 89); 27 Oct 2019 20:04:39 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=Wolff, wolff, Manager X-HELO: smtp-out-no.shaw.ca Received: from smtp-out-no.shaw.ca (HELO smtp-out-no.shaw.ca) (64.59.134.12) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 27 Oct 2019 20:04:37 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id Oom9ipamcUIS2OomAirmJV; Sun, 27 Oct 2019 14:04:35 -0600 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: OPENMPI only works on Cygwin Terminal not windows Command Line To: cygwin@cygwin.com References: From: Brian Inglis Openpgp: preference=signencrypt Message-ID: Date: Sun, 27 Oct 2019 20:04:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-10/txt/msg00172.txt.bz2 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 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