voxl-portal build failed on m1 max macbook pro



  • Hi team,
    I tried to build the voxl-portal on MacBook pro with m1 max, but it's failed with the make error "error: the clang compiler does not support '-march=armv7-a'"

    I checked the CMakeLists.txt of voxl-portal, and it's configured with "-march=armv7-a". So, I am wondering if compiling VOXL on m1 chip is available? Or I could modify any settings to address it? I would make some modifications to VOXL SDK for my project use, so I would consider building a local version.

    This is the info of my local clang compiler for your reference:

    Apple clang version 13.0.0 (clang-1300.0.29.30)
    Target: arm64-apple-darwin21.3.0
    Thread model: posix
    InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
    Available CPUs for this target:
    
    	a64fx
    	apple-a10
    	apple-a11
    	apple-a12
    	apple-a13
    	apple-a14
    	apple-a7
    	apple-a8
    	apple-a9
    	apple-latest
    	apple-m1
    	apple-s4
    	apple-s5
    	carmel
    	cortex-a34
    	cortex-a35
    	cortex-a53
    	cortex-a55
    	cortex-a57
    	cortex-a65
    	cortex-a65ae
    	cortex-a72
    	cortex-a73
    	cortex-a75
    	cortex-a76
    	cortex-a76ae
    	cortex-a77
    	cortex-a78
    	cortex-a78c
    	cortex-r82
    	cortex-x1
    	cyclone
    	exynos-m3
    	exynos-m4
    	exynos-m5
    	falkor
    	generic
    	kryo
    	lightning
    	neoverse-e1
    	neoverse-n1
    	neoverse-n2
    	neoverse-v1
    	saphira
    	thunderx
    	thunderx2t99
    	thunderx3t110
    	thunderxt81
    	thunderxt83
    	thunderxt88
    	tsv110
    	vortex
    
    Use -mcpu or -mtune to specify the target's processor.
    For example, clang --target=aarch64-unknown-linux-gui -mcpu=cortex-a35
    
    

    Thanks.


  • Dev Team

    @yu-zhang The correct branch to use is "dev" for this project. The README.md for that branch explains the build process: https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-portal/-/blob/dev/README.md. You need to build it in one of our build Dockers.



  • @Eric-Katzfey Thanks for the information, and I will have a try then 😉


Log in to reply