Steve,
On Mon, Jun 7, 2010 at 5:43 AM, Steve M. Robbins <[email protected]> wrote: > The mpi-defaults control file specifies lam for sparc, check > the buildd log: > > > https://buildd.debian.org/fetch.cgi?pkg=mpi-defaults&arch=sparc&ver=0.6&stamp=1246463638&file=log&as=raw > > As far as I can tell, Boost is consistent. The problem lies > elsewhere. > 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! somehow life picks openmpi and compiles some boost::mpi function with it whereas boost::mpi was compiled with lam hence the linkage problems. Lam is the default on sparc but somehow cmake script FindMPI.cmake picked openmpi - Found MPI: /usr/lib/openmpi/lib/libmpi_cxx.so here is where FindMPI looks for mpi set(_MPI_PACKAGE_DIR mpi mpich openmpi lib/mpi lib/mpich lib/openmpi "MPICH/SDK" "Microsoft Compute Cluster Pack" ) If you look here https://buildd.debian.org/fetch.cgi?pkg=life&arch=sparc&ver=0.9.24-4&stamp=1275756138&file=log&as=raw it installs lam and openmpi and some packages like hdf5 are specifically installed with openmpi support. 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 ? I found this in FindMPI.cmake # If CMake initially finds a different MPI than was intended, and you # want to use the MPI compiler auto-detection for a different MPI # implementation, set MPI_COMPILER to the MPI compiler driver you want # to use (e.g., mpicxx) and then set MPI_LIBRARY to the string # MPI_LIBRARY-NOTFOUND. When you re-configure, auto-detection of MPI # will run again with the newly-specified MPI_COMPILER. I will try that ASAP. Best regards C.
