DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=v53hzaKbAEeWeIMFuE6gfDlSm4mW8
	e8yW45NljpAGth8U2dskBiFGdw9PQRoZnEitmFbc8Z8KPn16RbHPtDxNz9qV9diN
	cHu4yU/bswyStbcnjDKZ4h1glvwupYARUKHiqhs8j/ONHh6KaKsErrEUeyWbdEuB
	9jkPj25sZ3LzrA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: Andy May <ajmay81@gmail.com>
Date: Thu, 13 Sep 2018 08:50:06 +0100
Message-ID: <CAMurBn+p-80xPpEyWH9N4R5cZYoEaveLKFHYg=E+cN5+SWqTaA@mail.gmail.com>
Subject: openmpi 3.1.2 missing mpicxx
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

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?

Many thanks,

Andy

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