Hi Adam,<div><br></div><div>thanks for your answer !<br><br><div class="gmail_quote">On Fri, Jun 11, 2010 at 8:05 PM, Adam C Powell IV <span dir="ltr"><<a href="mailto:hazelsct@debian.org">hazelsct@debian.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">If mpi-default-dev points to lam, then why is OpenMPI installed in the<br>
system? Just use mpi-default-dev and libhdf5-mpi-dev and they should be<br>
consistent. If they're not, then HDF5 needs a bin NMU.<br></blockquote><div>I am not depending on hdf5, it gets installed due to another build-depends (I am not sure which one)</div><div>I of course use mpi-default-dev which points to lam</div>
<div>unfortunately openmpi gets installed too and has higher priority than lam and all the defaults point to openm pi</div><div>mpic++, incluce, libs...</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Likewise with boost, that should be built using mpi-default-dev, right?<br></blockquote><div>boost is also build-depending on mpi-default-dev</div><div><br></div><div>I believe neither life or boost are at fault but rather mpi-default* which has an inconsistent behavior on sparc</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Are you suggesting that mpi-default-dev should conflict with every<br>
non-default mpi-dev package on a given architecture, to make certain<br>
that nobody has it installed when building such packages?<br></blockquote><div>no </div><div>I suggest that if lam is the default implementation then it should be the default</div><div>if openmpi is installed it becomes the default</div>
<div>log on <a href="http://smetana.debian.org">smetana.debian.org</a> and do ' dchroot unstable' and check for yourself.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
[Separate issue: if there's openmpi on Sparc, why is it not the<br>
mpi-default?]<br></blockquote><div>good question.</div><div><br></div><div> I fixed the problem by enforcing lam</div><div>I set the MPI_COMPILER to mpic++.lam explicitely rather than mpic++ which points to the openmpi one</div>
<div><br></div><div>also there is a mpicxx for openmpi but none for lam . So the alternatives are not consistent</div><div>should I fill a bug on mpi-default* ?</div><div><br></div><div>Best regards</div><div>C.</div></div>
</div>