Re: [Boost-users] [EXTERNAL] Re: [MPI] missing symbols using serialization's static library design

Subject: Re: [Boost-users] [EXTERNAL] Re: [MPI] missing symbols using serialization's static library design
From: Matthias Troyer (troyer_at_[hidden])
Date: 2012-10-30 17:38:43

On Oct 18, 2012, at 5:26 PM, "Barrett, Brian W" <bwbarre_at_[hidden]> wrote:

> On 10/17/12 1:00 PM, "Robert Ramey" <ramey_at_[hidden]> wrote:
> 
>> Barrett, Brian W wrote:
>>> 
>>> I know how to determine which MPI archivers need to be explicitly
>>> instantiated, but as I said, that's a rather unsatisfying answer to
>>> the problem.  It appears that the list of archivers I have to
>>> explicitly instantiate has changed along the way from Boost 1.43.0
>>> (the version that was current when we started the project) and Boost
>>> 1.51.0.  At least one of the archivers is in the detail namespace, so
>>> the authors clearly believe such details are internal to the
>>> implementation.  This puts us in a rather large support bind.  I was
>>> hoping that there would be a better way (like a macro to help with
>>> the explicit instantiation or something similar.
>> 
>> How about suggesting a patch to the MPI serialization inplementation
>> which would sync this implementation up with the others.
> 
> Unfortunately, I'm barely competent in using Boost.MPI and
> Boost.Serialization.  I'm definitely not in a position to be able to apply
> a patch.
> 
> What I'm getting from your responses and the general silence elsewhere is
> that the right answer is to deal with the incompatibilities between
> versions of Boost and explicitly instantiate all the internal MPI
> archivers and hope for the best.  It's a little painful, but I think we
> can do that.

can you send me a test code that shows the problem and I will try to resolve your issue? ALso, which hardware platform are you trying to compile it on?

Matthias