On 24 Mar, Kay Schenk wrote:
>
>
> On 03/24/2016 03:09 PM, Don Lewis wrote:
>> On 22 Mar, Kay Schenk wrote:
>>>
>>> On 03/21/2016 06:14 PM, Don Lewis wrote:
When building OpenOffice with recent versions of clang, an extreme
number of very verbose warnings are generated by the Boost head
On 03/24/2016 03:09 PM, Don Lewis wrote:
> On 22 Mar, Kay Schenk wrote:
>>
>> On 03/21/2016 06:14 PM, Don Lewis wrote:
>>> When building OpenOffice with recent versions of clang, an extreme
>>> number of very verbose warnings are generated by the Boost headers,
>>> which basically doubles the siz
On 22 Mar, Kay Schenk wrote:
>
> On 03/21/2016 06:14 PM, Don Lewis wrote:
>> When building OpenOffice with recent versions of clang, an extreme
>> number of very verbose warnings are generated by the Boost headers,
>> which basically doubles the size of the build log.
>>
>> For the FreeBSD port,
On 03/21/2016 06:14 PM, Don Lewis wrote:
> When building OpenOffice with recent versions of clang, an extreme
> number of very verbose warnings are generated by the Boost headers,
> which basically doubles the size of the build log.
>
> For the FreeBSD port, which uses the system Boost (still 1.5
Hi Don;
The right thing would be to update boost, however this usually involves
checking
that builds continue to work for other platforms, including the old MSVC
compiler
we use for AOO.
Of course we have buildbots for that, but generally I am afraid it may
be work that
doesn't pay on the lo
When building OpenOffice with recent versions of clang, an extreme
number of very verbose warnings are generated by the Boost headers,
which basically doubles the size of the build log.
For the FreeBSD port, which uses the system Boost (still 1.55 for now),
I fixed this by cherry picking a number
