Re: [boost] [1.56.0] Release candidates available

Subject: Re: [boost] [1.56.0] Release candidates available
From: Beman Dawes (bdawes_at_[hidden])
Date: 2014-07-30 10:02:43

On Tue, Jul 29, 2014 at 2:51 PM, Menelaos Karavelas <
menelaos.karavelas_at_[hidden]> wrote:

>
> On 29/07/2014 09:40 μμ, Marshall Clow wrote:
>
>> On Jul 29, 2014, at 10:06 AM, Marshall Clow <mclow.lists_at_[hidden]>
>> wrote:
>>
>>  Release candidate files for 1.65.0 are available at
>>> http://boost.cowic.de/rc/
>>>
>> Ok, ok - fine. 1.56.0
>>
>>  As always, the release managers would appreciate it if you download
>>> the candidate of your choice and give building it a try. Please report
>>> both success and failure, and anything else that is noteworthy.
>>>
>>> This helps ensure the candidates build OK before we push them out to
>>> SourceForge.
>>>
>>> The files (and associated md5s) are:
>>>         MD5 (boost_1_56_0_rc1.7z)               =
>>> 0ac22b92b24209286d48e4c41925cd9f
>>>         MD5 (boost_1_56_0_rc1.tar.bz2)  = 5b5bfa99244b1ac5737323decceb19
>>> c2
>>>         MD5 (boost_1_56_0_rc1.tar.gz)   = 2047cdd4e09cda34e7f10fec0f8211
>>> 75
>>>         MD5 (boost_1_56_0_rc1.zip)              =
>>> 0c544f6acc85550b15cdc9221f2ac0c9
>>>
>> I have successfully built using gcc 4.9.0 and clang 3.4 on Mac OS X 9.4.
>>
>
> Same here on ubuntu 13.10 with gcc 4.8 and clang 3.2.
> A lot of unused local typedef warnings on gcc 4.8 and A LOT of warnings
> with clang (almost 46 MB build log file).
>

While we do not want to hold the release to clear warnings, once the
release ships we might want to have a sprint to clear warnings.

Thanks,

--Beman