From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: libmpi_cxx.dll.a missing
Date: Wed, 29 Aug 2018 20:21:00 -0000 [thread overview]
Message-ID: <e328a2e3-f94e-eb56-f1b4-41d3b0b1b325@gmail.com> (raw)
In-Reply-To: <08d4e3d4-3175-aabb-376f-09bc5b51ae97@dronecode.org.uk>
Am 29.08.2018 um 13:15 schrieb Jon Turney:
> On 28/08/2018 12:12, Marco Atzeri wrote:
>> Am 28.08.2018 um 11:24 schrieb Antonio Pio Rinaldi:
>>> Hello,
>>>
>>
>> The C++ interface was removed on the upstream version of OpenMPI.
>>
>> https://blogs.cisco.com/performance/the-mpi-c-bindings-what-happened-and-why
>>
>> The suggested solution is to use the C interface
>
> I believe OpenMPI now has a configuration option, --enable-mpi-cxx,
> which enables these deprecated interfaces to be built.
>
> I was going to ask you if not using that was a deliberate choice, since
> this also breaks a meson test case.
>
I was thinking to remove on next release
/usr/bin/mpic++ -> opal_wrapper.exe
/usr/bin/mpicxx -> opal_wrapper.exe
because clearly make no sense to have them when the C++
interface is not anymore present.
This is a upstream inconsistency
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
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:[~2018-08-29 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 17:45 Antonio Pio Rinaldi
2018-08-28 20:31 ` Marco Atzeri
2018-08-29 12:26 ` Jon Turney
2018-08-29 20:21 ` 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=e328a2e3-f94e-eb56-f1b4-41d3b0b1b325@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).