Build breaks with: libs/context/src/asm/jump_arm_aapcs_elf_gas.S:55: Error: selected processor does not support `vstmia sp,{d8-d15}' libs/context/src/asm/jump_arm_aapcs_elf_gas.S:66: Error: selected processor does not support `vldmia sp,{d8-d15}' libs/context/src/asm/ontop_arm_aapcs_elf_gas.S:55: Error: selected processor does not support `vstmia sp,{d8-d15}' libs/context/src/asm/ontop_arm_aapcs_elf_gas.S:69: Error: selected processor does not support `vldmia sp,{d8-d15}'
Which FreeBSD version? What port options have you selected? Can you /etc/make.conf contents? Are you building on real hardware or via qemu-user-static? - boost-libs-1.64.0 builds fine on 12.0 armv6: http://beefy8.nyi.freebsd.org/data/head-armv6-default/p445465_s320884/logs/boost-libs-1.64.0.log - boost-libs-1.64.0 builds fine on 11.0 armv6: http://beefy15.nyi.freebsd.org/data/110armv6-quarterly/445595/logs/boost-libs-1.64.0.log (ipv6-only) - boost-libs-1.65.0 (from bug 220714) builds fine on 11.1 armv6: http://sprunge.us/WOeR
Building with Poudriere 10.3-RELEASE r297553 and qemu-arm version 2.8.50. Host is 11.0-RELEASE-p8. make.conf is empty and option file contains: # Options for boost-libs-1.64.0 _OPTIONS_READ=boost-libs-1.64.0 _FILE_COMPLETE_OPTIONS_LIST=DEBUG OPTIMIZED_CFLAGS ICONV ICU OPTIONS_FILE_UNSET+=DEBUG OPTIONS_FILE_SET+=OPTIMIZED_CFLAGS OPTIONS_FILE_SET+=ICONV OPTIONS_FILE_SET+=ICU Same result with: OPTIONS_FILE_UNSET+=OPTIMIZED_CFLAGS Maybe 10.3 specific build error?
Additional note: Same environment with 11.0-RELEASE-p1 r306421 yields a successful build.
Do you have a particular reason to stay on 10.3? armv6 probably has only Tier3 support before 11.0. https://pkg-status.freebsd.org/ lacks 10.3 armv6 builders, so neither binary packages are available nor how many ports successfully built. > Maybe 10.3 specific build error? Try to use devel/llvm40, lang/gcc or install binutils package then add -no-integrated-as to CFLAGS. toolchain@ may know more how usable base Clang 3.4 on 10.3 armv6 for building ports.
(In reply to Jan Beich from comment #4) No reason to stay on 10.3 and also I was not aware of the Tier3 status. Thanks for enlightening me.
Can portmgr clarify ports support for Tier2 and Tier3 on various releases? When exactly did armv6 and aarch64 became Tier2? For one, 10.3 ia64 (Tier2) support is routinely gets trimmed from ports ahead of /stable/10 EOL. For two, sparc64 (Tier2) support in ports seems to be worse than mips64 (Tier3).