Re: [boost] [EXTERNAL] [1.61.0] Master branch is closed

Subject: Re: [boost] [EXTERNAL] [1.61.0] Master branch is closed
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2016-04-26 14:01:07

> On Apr 26, 2016, at 11:47 AM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> 
> On Tue, Apr 26, 2016 at 3:36 AM, alainm <alain.miniussi_at_oca.eu> wrote:
> 
>> 
>> 
>> On 25/04/2016 21:12, Rene Rivera wrote:
>> 
>>> On Mon, Apr 25, 2016 at 2:05 PM, Belcourt, Kenneth <kbelco_at_[hidden]>
>>> wrote:
>>> 
>>> On Apr 25, 2016, at 12:08 PM, Vladimir Prus <vladimir.prus_at_[hidden]>
>>>>> 
>>>> wrote:
>>>> 
>>>>> On 4/23/2016 10:02 PM, Belcourt, Kenneth wrote:
>>>>> 
>>>>>> It’d be nice if serialization worked with MPI for the release, though
>>>>>> 
>>>>> I’m not sure it’s a show stopper.
>>>> 
>>>>> What is the actual impact of this problem? E.g. which percentage of MPI
>>>>> 
>>>> users will find their code
>>>> 
>>>>> no longer compiling?
>>>>> 
>>>> Fair question, no idea really.  I know that Boost MPI's used on multiple
>>>> projects where I work, though it’s easy enough for us to just skip using
>>>> the 1.61 release to avoid breaking our MPI serialization code.
>>>> 
>>>> Sorry if my ignorance of how MPI shows :-) .. How much of MPI is usable
>>> with this problem? Is it usable at all? Is it partially usable?
>>> 
>>> No part of Boost MPI is usable, meaning no code built on top of Boost.MPI
>> will compile.
>> 
>> Just tried.
>> 
> 
> Thanks for the info.. But given that we don't have *any* test results with
> MPI passing (i.e. nothing on develop yet).. I'm afraid it's going to stay
> broken this release.

I just applied a patch that should get all of graph, graph_parallel, and MPI passing on develop.  Tomorrow should be clean, if you can wait that long.

Noel