<html>#2578: Kranc, Cactus, and MPI linking issues
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Nicholas Hugh Olsen</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2021_05</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>If it’s Kranc specific then you may consider using Kranc’s mailng list and issue tracker as mentioned on the Kranc website: <a data-is-external-link="true" href="http://kranccode.org/support.html" rel="nofollow">http://kranccode.org/support.html</a></p>
<p>Having said that, the Kranc authors tend to see ET tickets and may speak up.</p>
<div class="codehilite"><pre><span></span><span>~$ ls /usr/lib/x86_64-linux-gnu/openmpi/lib/</span>
<span>libmca_common_monitoring.so libmpi_cxx.so libopen-rte.so</span>
<span>libmca_common_ofi.so libmpi_java.so liboshmem.so</span>
<span>libmca_common_ompio.so libmpi_mpifh.so ompi_monitoring_prof.so</span>
<span>libmca_common_sm.so libmpi_usempi_ignore_tkr.so openmpi3</span>
<span>libmca_common_ucx.so libmpi_usempif08.so pkgconfig</span>
<span>libmca_common_verbs.so libompitrace.so</span>
<span>libmpi.so libopen-pal.so</span>
</pre></div>
<p>ie there is a library <code>mpi_cxx</code> in addition to <code>mpi</code>.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2578/kranc-cactus-and-mpi-linking-issues'>https://bitbucket.org/einsteintoolkit/tickets/issues/2578/kranc-cactus-and-mpi-linking-issues</a></p>
</html>