[boost] [1.56.0] Release Candidate 3 available

We've created a third release candidate to fix a one more issue with Boost.Range. The files for 1.56.0 RC3 are available at: http://boost.cowic.de/rc/ 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. The files (and associated md5s) are: MD5 (./boost_1_56_0_rc3.7z) = b7a72a6a6f487fa445333b4e115c6171 MD5 (./boost_1_56_0_rc3.tar.bz2) = a744cf167b05d72335f27c88115f211d MD5 (./boost_1_56_0_rc3.tar.gz) = 8c54705c424513fa2be0042696a3a162 MD5 (./boost_1_56_0_rc3.zip) = fc16da21d641e03715a4144cb093964e Thanks! -- The release managers

On Aug 5, 2014, at 2:19 PM, Marshall Clow
We've created a third release candidate to fix a one more issue with Boost.Range.
The files for 1.56.0 RC3 are available at: http://boost.cowic.de/rc/
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.
The files (and associated md5s) are: MD5 (./boost_1_56_0_rc3.7z) = b7a72a6a6f487fa445333b4e115c6171 MD5 (./boost_1_56_0_rc3.tar.bz2) = a744cf167b05d72335f27c88115f211d MD5 (./boost_1_56_0_rc3.tar.gz) = 8c54705c424513fa2be0042696a3a162 MD5 (./boost_1_56_0_rc3.zip) = fc16da21d641e03715a4144cb093964e
Thanks! -- The release managers
Built successfully on Mac OS X: gcc 4.9.0 clang in C++03/11/14 — Marshall

Marshall Clow
We've created a third release candidate to fix a one more issue with Boost.Range.
The files for 1.56.0 RC3 are available at: http://boost.cowic.de/rc/
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.
I have successfully built some real-life projects with MSVC 12 Update 3 RTM using the following configurations: link=static runtime-link=static/shared address-model=32/64 _WIN32_WINNT=0x502/0x601

On 05.08.2014 23:19, Marshall Clow wrote:
We've created a third release candidate to fix a one more issue with Boost.Range.
The files for 1.56.0 RC3 are available at: http://boost.cowic.de/rc/
Build errors I have encountered with rc3: Native x86_64-linux-gnu-gcc 4.8: Only expected errors, e.g. missing Python development headers. i686-w64-ming-gcc 4.8 cross-compiler: The assembler chokes on Boost.context, exact error message: gcc.compile.asm /home/rainer/projects/starfire/intermediate/libs/edge/boost_1_56_0/build_rainer6_mingw_i686-w64-mingw32_edge/boost/bin.v2/libs/context/build/gcc-mingw-4.8/debug/link-static/target-os-windows/threading-multi/asm/make_i386_sysv_elf_gas.o libs/context/src/asm/make_i386_sysv_elf_gas.S: Assembler messages: libs/context/src/asm/make_i386_sysv_elf_gas.S:23: Warning: .type pseudo-op used outside of .def/.endef ignored. libs/context/src/asm/make_i386_sysv_elf_gas.S:23: Error: junk at end of line, first unrecognized character is `m' libs/context/src/asm/make_i386_sysv_elf_gas.S:74: Warning: .size pseudo-op used outside of .def/.endef ignored. libs/context/src/asm/make_i386_sysv_elf_gas.S:74: Error: junk at end of line, first unrecognized character is `m' libs/context/src/asm/make_i386_sysv_elf_gas.S:77: Error: junk at end of line, first unrecognized character is `-' "i686-w64-mingw32-g++" -x assembler-with-cpp -O0 -fno-inline -Wall -g -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_SOURCE -I"." -c -o "/home/rainer/projects/starfire/intermediate/libs/edge/boost_1_56_0/build_rainer6_mingw_i686-w64-mingw32_edge/boost/bin.v2/libs/context/build/gcc-mingw-4.8/debug/link-static/target-os-windows/threading-multi/asm/make_i386_sysv_elf_gas.o" "libs/context/src/asm/make_i386_sysv_elf_gas.S" x86_64-w64-ming-gcc 4.8 cross-compiler: Same problem as the i686-w64-ming-gcc 4.8 cross-compiler above. arm-linux-androideabi gcc 4.8 cross-compiler: Link errors due to missing librt, exact error message: gcc.link.dll /home/rainer/projects/starfire/intermediate/libs/SDL2/boost_1_56_0/build_rainer6_gcc_arm-linux-androideabi_SDL2/boost/bin.v2/libs/atomic/build/gcc-4.8/release/threading-multi/libboost_atomic-mt.so.1.56.0 /home/rainer/projects/starfire/intermediate/android/gcc_arm-linux-androideabi/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lrt collect2: error: ld returned 1 exit status "arm-linux-androideabi-g++" -Wl,-R -Wl,"lib/gcc_arm-linux-androideabi_SDL2" -o "/home/rainer/projects/starfire/intermediate/libs/SDL2/boost_1_56_0/build_rainer6_gcc_arm-linux-androideabi_SDL2/boost/bin.v2/libs/atomic/build/gcc-4.8/release/threading-multi/libboost_atomic-mt.so.1.56.0" -Wl,-h -Wl,libboost_atomic-mt.so.1.56.0 -shared -Wl,--start-group "/home/rainer/projects/starfire/intermediate/libs/SDL2/boost_1_56_0/build_rainer6_gcc_arm-linux-androideabi_SDL2/boost/bin.v2/libs/atomic/build/gcc-4.8/release/threading-multi/lockpool.o" -Wl,-Bstatic -Wl,-Bdynamic -lrt -Wl,--end-group -pthread Boost.Context fails as expected. mipsel-linux-android gcc 4.8 cross-compiler: Same problem as the arm-linux-androideabi 4.8 cross-compiler above. I haven't tried clang yet. -- Rainer Deyke (rainerd@eldwood.com)

On Tue, Aug 5, 2014 at 9:19 PM, Marshall Clow
We've created a third release candidate to fix a one more issue with Boost.Range.
The files for 1.56.0 RC3 are available at: http://boost.cowic.de/rc/
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.
Looks good on windows: toolset arch compile install Link Execute msvc-8.0 32 X X X X msvc-8.0 64 X X X X msvc-9.0 32 X X X X msvc-9.0 64 X X X X msvc-10.0 32 X X X X msvc-10.0 64 X X X X msvc-11.0 32 X X X X msvc-11.0 64 X X X X msvc-12.0 32 X X X X msvc-12.0 64 X 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. Tom

Thanks to everyone who reported their RC results. The RC reporting coverage has been much better than for past releases, and that is very helpful indeed! --Beman
participants (5)
-
Beman Dawes
-
Marcel Raad
-
Marshall Clow
-
Rainer Deyke
-
Tom Kent