On Mon, Sep 26, 2016 at 5:06 PM, Tom Kent wrote:

Looks good on windows.

Patiently awaiting the SourceForge upload.

toolset arch compile Link Execute msvc-8.0 32 X X X msvc-8.0 64 X X X msvc-9.0 32 X X X msvc-9.0 64 X X X msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X

Compile means that the b2 command completed without errors Install means that the installers for the respective version were generated Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors.

Full build logs can be found here: https://gist.github.com/teeks99/7f2cad7df28b7c085c0dfc1a4a917277

Tom

On Mon, Sep 26, 2016 at 9:36 AM, Rene Rivera wrote:

...

The release candidates for the 1.62.0 release are now available at:

https://sourceforge.net/projects/boost/files/boost/1.62.0.rc.1/boost_1_62_0_...

https://sourceforge.net/projects/boost/files/boost/1.62.0.rc.1/boost_1_62_0_...

https://sourceforge.net/projects/boost/files/boost/1.62.0.rc.1/boost_1_62_0_...

https://sourceforge.net/projects/boost/files/boost/1.62.0.rc.1/boost_1_62_0_...

The SHA256 checksums are as follows:

b91c2cda8bee73ea613130e19e72c9589e9ef0357c4c5cc5f7523de82cce11f7 boost_1_62_0_rc1.7z 36c96b0f6155c98404091d8ceb48319a28279ca0333fba1ad8611eb90afb2ca0 boost_1_62_0_rc1.tar.bz2 440a59f8bc4023dbe6285c9998b0f7fa288468b889746b1ef00e8b36c559dce1 boost_1_62_0_rc1.tar.gz 084b2e0638bbe0975a9e43e21bc9ceae33ef11377aecab3268a57cf41e405d4e boost_1_62_0_rc1.zip

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.

Thanks, the release managers.

-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

On Mon, Sep 26, 2016 at 5:52 PM, Marshall Clow wrote:

On Mon, Sep 26, 2016 at 7:36 AM, Rene Rivera wrote:

...

The release candidates for the 1.62.0 release are now available at:

[snip]

Now to run some tests....

-- Marshall

The test "vmd/test/test_doc_modifiers_return_type.cpp" hangs clang. Reported as https://llvm.org/bugs/show_bug.cgi?id=30546 -- Marshall

On Tue, Sep 27, 2016 at 7:14 PM, Edward Diener wrote:

On 9/27/2016 9:24 PM, Marshall Clow wrote:

...

On Mon, Sep 26, 2016 at 5:52 PM, Marshall Clow mailto:mclow.lists@gmail.com> wrote:

On Mon, Sep 26, 2016 at 7:36 AM, Rene Rivera mailto:grafikrobot@gmail.com> wrote:

The release candidates for the 1.62.0 release are now available at:

[snip]

Now to run some tests....

-- Marshall

The test "vmd/test/test_doc_modifiers_return_type.cpp" hangs clang. Reported as https://llvm.org/bugs/show_bug.cgi?id=30546

Evidently clang runs out of memory. Note that with VC++ and gcc the test passes.

I don't know why clang would run out ot memory while VC++ and gcc do not but I have not queried the clang mailing list further about it. An educated guess is that clang calculates some fixed size for the preprocessor and when macro expansions cause that fixed size to overrun you get an out of memory condition. I can hardly believe that the preprocessor is really running out of virtual memory, no matter how complicated the preprocessor code gets in VMD.

When I was discussing the problem with Richard, he opined that that might be a problem, if the preprocessed source exceeded 1 GB in size - which it doesn't. (GCC expands this test to about 700K) So I suspect it is "just a bug" -- Marshall