Source: boost1.53 Version: 1.53.0-2 Severity: wishlist I noticed that in the latest upload of boost1.53 you addressed some build failures due to the context library having no support for some of the Debian archs. However, for example on x32 I'm still getting this:
<URL:http://buildd.debian-ports.org/status/fetch.php?pkg=boost1.53&arch=x32&ver=1.53.0-2&stamp=1363804423>: ... "g++" -x assembler-with-cpp -O3 -finline-functions -Wno-inline -Wall -g -D_FORTIFY_SOURCE=2 -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/context/build/gcc-4.7/release/debug-symbols-on/threading-multi/asm/jump_i386_sysv_elf_gas.o" "libs/context/src/asm/jump_i386_sysv_elf_gas.S" libs/context/src/asm/jump_i386_sysv_elf_gas.S: Assembler messages: libs/context/src/asm/jump_i386_sysv_elf_gas.S:71: Error: operand type mismatch for `jmp' ...failed gcc.compile.asm bin.v2/libs/context/build/gcc-4.7/release/debug-symbols-on/threading-multi/asm/jump_i386_sysv_elf_gas.o... gcc.compile.asm bin.v2/libs/context/build/gcc-4.7/release/debug-symbols-on/threading-multi/asm/make_i386_sysv_elf_gas.o "g++" -x assembler-with-cpp -O3 -finline-functions -Wno-inline -Wall -g -D_FORTIFY_SOURCE=2 -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/context/build/gcc-4.7/release/debug-symbols-on/threading-multi/asm/make_i386_sysv_elf_gas.o" "libs/context/src/asm/make_i386_sysv_elf_gas.S" libs/context/src/asm/make_i386_sysv_elf_gas.S: Assembler messages: libs/context/src/asm/make_i386_sysv_elf_gas.S:60: Error: invalid instruction suffix for `pop' libs/context/src/asm/make_i386_sysv_elf_gas.S:70: Error: invalid instruction suffix for `pop' ...failed gcc.compile.asm bin.v2/libs/context/build/gcc-4.7/release/debug-symbols-on/threading-multi/asm/make_i386_sysv_elf_gas.o... ... Looking at the logs from 1.53.0-1 on debian-ports.org, it seems there are also build failures on alpha, powerpcspe, ppc64, sh4 -- though I didn't look at those logs in detail to determine whether missing context support was the cause. There are also m68k and sparc64 which haven't gotten to a trial build yet. (And I'd ignore hppa which is completely out of date and hasn't seen any buildd activity whatsoever for quite a while.) Also, in the specific case of x32, from looking at the asm it looks like using the x86_64 asm files instead of i386 should work. -- Daniel Schepler -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
