Steve,<div><br></div><div><br></div><div><br><div class="gmail_quote">On Mon, Jun 7, 2010 at 5:43 AM, Steve M. Robbins <span dir="ltr"><<a href="mailto:steve@sumost.ca">steve@sumost.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":1v1" class="ii gt">The mpi-defaults control file specifies lam for sparc, check<br>
the buildd log:<br>
<br>
<a href="https://buildd.debian.org/fetch.cgi?pkg=mpi-defaults&arch=sparc&ver=0.6&stamp=1246463638&file=log&as=raw" target="_blank">https://buildd.debian.org/fetch.cgi?pkg=mpi-defaults&arch=sparc&ver=0.6&stamp=1246463638&file=log&as=raw</a><br>
<br>
As far as I can tell, Boost is consistent. The problem lies<br>
elsewhere.</div></blockquote></div>I think that's exactely where the problem is but the issue is not with boost::mpi but with the mixup between lam and openmpi packages!</div><div>somehow life picks openmpi and compiles some boost::mpi function with it whereas boost::mpi was compiled with lam hence the linkage problems.</div>
<div>Lam is the default on sparc but somehow cmake script FindMPI.cmake picked openmpi </div><div><span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre; ">- Found MPI: /usr/lib/openmpi/lib/libmpi_cxx.so</span></div>
<div><span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre; "><br></span></div><div><span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre; ">here is where FindMPI looks for mpi</span></div>
<div><span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre; "><br></span></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="white-space: pre; font-size: medium;">set(_MPI_PACKAGE_DIR
mpi
mpich
openmpi
lib/mpi
lib/mpich
lib/openmpi
"MPICH/SDK"
"Microsoft Compute Cluster Pack"
)</span></font><span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre; ">
</span></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="white-space: pre; font-size: medium;"><br></span></font></div><div><br></div><div>If you look here</div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>
<a href="https://buildd.debian.org/fetch.cgi?pkg=life&arch=sparc&ver=0.9.24-4&stamp=1275756138&file=log&as=raw">https://buildd.debian.org/fetch.cgi?pkg=life&arch=sparc&ver=0.9.24-4&stamp=1275756138&file=log&as=raw</a> </div>
<div><br></div><div>it installs lam and openmpi and some packages like hdf5 are specifically installed with openmpi support. </div><div>On my side life depends solely on mpi-default-dev, it seems that some other package don't (e.g. hdf5), isn't it a problem ?</div>
<div><br></div><div>I found this in FindMPI.cmake</div><div><br></div><div><div># If CMake initially finds a different MPI than was intended, and you</div><div># want to use the MPI compiler auto-detection for a different MPI</div>
<div># implementation, set MPI_COMPILER to the MPI compiler driver you want</div><div># to use (e.g., mpicxx) and then set MPI_LIBRARY to the string</div><div># MPI_LIBRARY-NOTFOUND. When you re-configure, auto-detection of MPI</div>
<div># will run again with the newly-specified MPI_COMPILER.</div></div><div><br></div><div>I will try that ASAP.</div><div><br></div><div>Best regards</div><div>C.</div><div><br></div>