From: Andrey Repin <anrdaemon@yandex.ru>
To: Thomas Wolff <towo@towo.net>, cygwin@cygwin.com
Subject: Re: OPENMPI only works on Cygwin Terminal not windows Command Line
Date: Mon, 28 Oct 2019 17:35:00 -0000 [thread overview]
Message-ID: <46883832.20191028202025@yandex.ru> (raw)
In-Reply-To: <bb6c2e33-d5e6-08a0-0354-5ba2a8815373@towo.net>
Greetings, Thomas Wolff!
> Am 27.10.2019 um 19:56 schrieb William John:
>> 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.
I would strongly discourage from hardlinking executable files, especially
those not explicitly controlled by you.
Next time you reinstall the package that contains the origin files, you will
get file versions mismatch between new requisite DLL's and then-linked main
executable.
If you need a link, create native symlink.
--
With best regards,
Andrey Repin
Monday, October 28, 2019 20:18:04
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
next prev parent reply other threads:[~2019-10-28 17:35 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
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 ` Andrey Repin [this message]
2019-10-28 17:20 ` OPENMPI only works on Cygwin Terminal not windows Command Line 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=46883832.20191028202025@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=towo@towo.net \
/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).