From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: libmpi_cxx.dll.a missing
Date: Tue, 28 Aug 2018 20:31:00 -0000 [thread overview]
Message-ID: <e2e57b6b-6d76-75ce-79d6-c2acf0fe8c5e@gmail.com> (raw)
In-Reply-To: <C6C4A713-424D-4A18-A201-1B642759E80E@gmail.com>
Am 28.08.2018 um 11:24 schrieb Antonio Pio Rinaldi:
> Hello,
>
> while trying to compile a code with cmake (GNU compiler 7.4 and cmake 3.6, latest cygwin), I got an error regarding mpicxx not being able to locate the library -lmpi_cxx.
> This was kind of weird, as I had installed the same code in another machine some time ago (with GNU compiler 6.4 and cmake 3.3, cygwin version 2.8) and did not have this issue.
>
> Then by navigating to the cygwin lib folder, I noticed that the file libmpi_cxx.dll.a was missing in the latest version (although the package Libs/libopenmpicxx1 seems to be installed).
>
> After copying the library file from the previous version I am able to correctly install my code.
>
> I am not sure whether this is a bug, or if I have to set up something else to let cygwin install the mpicxx library.
>
> Regards,
> Antonio Pio Rinaldi
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
Regards
Marco
---
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
next prev parent reply other threads:[~2018-08-28 11:13 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 [this message]
2018-08-29 12:26 ` Jon Turney
2018-08-29 20:21 ` Marco Atzeri
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=e2e57b6b-6d76-75ce-79d6-c2acf0fe8c5e@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).