From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: cygport dropping *.exe links
Date: Fri, 15 Aug 2014 11:26:00 -0000 [thread overview]
Message-ID: <53EDEE67.6070501@gmail.com> (raw)
Hi Yaakov,
I just noted a strange effect
during installation phase of openmpi a certain numbers of links to exe
files are created as
(cd /pub/devel/openmpi/64bit/openmpi-1.8.2rc4-1.x86_64/inst/usr/bin; rm
-f mpirun.exe; ln -s orterun.exe mpirun.exe)
and they are there during the cyginstall
$ ls ../inst/usr/bin/
cygmpi_cxx-1.dll cygopen-pal-6.dll mpicxx mpifort
ompi-ps.exe ortecc orte
cygmpi_mpifh-2.dll cygopen-rte-7.dll mpiexec.exe mpirun.exe
ompi-server.exe orte-clean.exe orte
cygmpi_usempi-1.dll mpic++ mpif77 ompi_info.exe
ompi-top.exe orted.exe orte
cygmpi-1.dll mpicc mpif90 ompi-clean.exe
opal_wrapper.exe orte-info.exe orte
but at post cyginstall phase they are gone:
$ ls ../inst/usr/bin/
cygmpi_cxx-1.dll cygmpi-1.dll mpic++ mpif77 ompi_info.exe
orte-clean.exe orte-ps.exe
cygmpi_mpifh-2.dll cygopen-pal-6.dll mpicc mpif90
opal_wrapper.exe orted.exe orterun.exe
cygmpi_usempi-1.dll cygopen-rte-7.dll mpicxx mpifort ortecc
Is it possible that latest binutils update is fooling cygport ?
In the past, it seems they were renamed ( mpirun.exe to mpirun)
https://cygwin.com/packages/x86/openmpi/openmpi-1.7.5-1
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
next reply other threads:[~2014-08-15 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 11:26 Marco Atzeri [this message]
2014-08-15 14:47 ` Marco Atzeri
2014-08-15 15:16 ` Corinna Vinschen
2014-08-15 17:02 ` Eric Blake
2014-09-01 8:52 ` Marco Atzeri
2014-09-24 3:35 ` Eric Blake
2014-10-08 12:55 ` Corinna Vinschen
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=53EDEE67.6070501@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).