[Boost-users] [chrono][system][timer][unit_test_framework] Unexpected static libraries in 1.63 (was [build])

Subject: [Boost-users] [chrono][system][timer][unit_test_framework] Unexpected static libraries in 1.63 (was [build])
From: Gavin Lambert (gavinl_at_[hidden])
Date: 2017-03-17 04:11:29

On 13/03/2017 18:33, I wrote:
> On 2/03/2017 12:28, I wrote:
>> I've recently rebuilt Boost 1.63 locally for both Windows and Linux,
>> requesting dynamic libraries only (link=dynamic).  However several
>> libraries are still being built in both static and dynamic forms:
>>
>>  - chrono
>>  - system
>>  - timer
>>  - unit_test_framework
>>
>> Additionally some libraries are being built only in static forms:
>>
>>  - exception
>>  - test_exec_monitor
>>
>> I assume the latter is intentional, as presumably some libraries can
>> only work as static libraries.  Is the former intentional or a bug?  It
>> seems like a bug.  Or do these contain symbols that the dynamic
>> libraries do not?
>
> Any chance the former group of libraries can be fixed before 1.64?

Trying again with individual library subject tags.  Or should I just 
give up on this and file github issues instead?