<div class="gmail_quote">2009/11/4 troy d. straszheim <span dir="ltr">&lt;<a href="mailto:troy@resophonic.com">troy@resophonic.com</a>&gt;</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

<div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There is still a small issue, though, with a mpi.so library <br>
</blockquote>
<br></div>That is not an error.  This is the python extension for MPI.  Python extensions are loaded by python, they don&#39;t start with &#39;lib&#39;.   If you add the directory containing mpi.so to your PYTHONPATH and execute<br>

<div class="im">
<br></div>
  &gt;&gt;&gt; import mpi<br>
<br>
that file should be found and loaded.  mpi.so will pull in libboost_python.so and libboost_mpi.so, so you may need to add the lib dir to your LD_LIBRARY_PATH as well.</blockquote><div><br>As such, the (Python extension) mpi.so library cannot be included in any RPM package, because it has no soname. Is there a CMake configuration option, so that that mpi.so library gets a proper soname?<br>

<br>Moreover, it could be a good idea to deliver it in a dedicated sub-directory, for instance /usr/lib[64]/python2.6 or /usr/lib[64]/python2.6/boost, because if left in /usr/lib[64], there is no hint as to what that library is aimed at.<br>

Do you know whether there is a CMake configuration option for that as well?<br><br>Thanks in advance<br><br>Best Regards<br><br>Denis<br></div></div>

