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)