public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: openmpi 3.1.2 missing mpicxx
Date: Thu, 13 Sep 2018 10:22:00 -0000	[thread overview]
Message-ID: <32ba9164-7fb6-48d4-df5a-9b5643bfeafb@gmail.com> (raw)
In-Reply-To: <CAMurBn+p-80xPpEyWH9N4R5cZYoEaveLKFHYg=E+cN5+SWqTaA@mail.gmail.com>

Am 13.09.2018 um 09:50 schrieb Andy May:
> Hi,
>
> The openmpi package version 3.1.2 no longer contains the mpicxx compiler
> wrapper, which is present in 3.1.1 package. In the package update
> announcement this is explicitly mentioned:
>
> https://cygwin.com/ml/cygwin/2018-09/msg00099.html
>
> as being depreciated. I know that the C++ bindings for MPI have certainly
> been depreciated, but the mpicxx wrapper itself is not; there are lots of
> C++ programs that use MPI by using the C bindings. Certainly this was the
> reason that was given for not removing mpicxx when someone suggested it:
>
> https://github.com/open-mpi/ompi/issues/1686
>
> Would it be possible to reinstate the mpicxx wrapper?

mpic++ and mpicxx are just links to opal_wrapper.exe
you can reinstate by yourself

> Many thanks,
>
> Andy
>


---
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

      reply	other threads:[~2018-09-13 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13  7:50 Andy May
2018-09-13 10:22 ` 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=32ba9164-7fb6-48d4-df5a-9b5643bfeafb@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).