From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: OpenMPI installation bug: /usr/bin/mpif90 links to non-existent target
Date: Thu, 30 Apr 2015 06:45:00 -0000 [thread overview]
Message-ID: <5541CF70.70204@gmail.com> (raw)
In-Reply-To: <CALLo=nrDwOb8sezZoq_TjZ_kQocNFat+wmjtfUpYG6TMsDph2Q@mail.gmail.com>
On 4/30/2015 3:32 AM, Mark Hadfield wrote:
> I have the current versions of openmpi and libopenmpi installed in
> Cygwin-64. The mpif90 command (MPI wrapper for Gfortran) does not
> execute, even though /usr/bin/mpif90 exists. The problem is that
> /usr/bin/mpif90 is a symbolic link to /usr/bin/mpifort.exe, which does
> not exist. However /usr/bin/mpifort does exist (and is itself a link
> to /usr/bin/opal_wrapper.exe). I have cured this by changing the
> target of /usr/bin/mpif90:
>
> $ ln -sf /usr/bin/mpifort /usr/bin/mpif90
>
> Mark Hadfield
> 51 Volga St
> Wellington 6023, NZ
>
Yes, I know.
you can also use
ln -sf usr/bin/opal_wrapper.exe /usr/bin/mpif90
ln -sf usr/bin/opal_wrapper.exe /usr/bin/mpif77
It is due to the interation of openmpi double link
and cygport post-install rename of links.
1.8.5 will not have the issue, as I proposed a patch upstream
https://github.com/open-mpi/ompi-release/commit/1147ddee73e84f80e27799e77391fc74033a6391
Regards
Marco
--
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
prev parent reply other threads:[~2015-04-30 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 1:32 Mark Hadfield
2015-04-30 6:45 ` Marco Atzeri [this message]
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=5541CF70.70204@gmail.com \
--to=marco.atzeri@gmail.com \
--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).