From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Hard links [was: Re: OPENMPI only works on Cygwin Terminal not windows Command Line]
Date: Mon, 28 Oct 2019 04:59:00 -0000 [thread overview]
Message-ID: <94318bef-1db5-6220-5b05-c16d8dcb40a2@towo.net> (raw)
In-Reply-To: <b060cbdb-c3e9-e08d-eba2-763e5fc97d88@SystematicSw.ab.ca>
Am 27.10.2019 um 21:04 schrieb Brian Inglis:
> On 2019-10-27 13:21, Thomas Wolff wrote:
> ...
>> 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
Additional privileges are required for Windows *soft* links. Hard links have always worked without. You can use cygwin ln alike.
--
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-28 4:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 3:33 OPENMPI only works on Cygwin Terminal not windows Command Line 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
2019-10-28 4:59 ` Thomas Wolff [this message]
2019-10-28 17:35 ` Andrey Repin
2019-10-28 17:20 ` Andrey Repin
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=94318bef-1db5-6220-5b05-c16d8dcb40a2@towo.net \
--to=towo@towo.net \
--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).