https://docs.google.com/document/d/1u-HAFfjWIH3WY3xajuGxGii-lWi1rpf16hVmB-mRdTA/edit# contains my findings about building V8 on Linux-arm64 when I tried it last year. I don't remember whether I saw the exact same assertion failure. https://chromium-review.googlesource.com/c/v8/v8/+/2743889 should have taught gm.py to do the right thing automatically; if you're not using gm.py you may want to replicate what it does.
On Mon, Aug 1, 2022 at 11:35 AM Leszek Swirski <[email protected]> wrote: > Hi Jeroen, > > That sounds plausible, could you share your args.gn file? You may be able > to fix this by setting your target_cpu there. > > - Leszek > > On Mon, Aug 1, 2022 at 11:06 AM Jeroen Ooms <[email protected]> wrote: > >> I maintain V8 bindings for the R programming language, for which we >> provide static v8 libraries for the most common distros, including one for >> alpine linux, and an arm64 build cross compiled on Debian. The builds are >> dockerized and automated in ci: https://github.com/jeroen/build-v8-static >> >> Now a user has requested an arm64 binary for alpine, but I am having a >> hard time making this work. Afaict, alpine has no cross compilers. So I >> tried to build it natively on arm64 hardware (docker on m1) but the build >> fails with: >> >> Assertion failed. >> assert(v8_snapshot_toolchain != "",\n^-----\nDo not know how to build a >> snapshot for //build/toolchain/linux:clang_x64 on linux arm64 >> See //BUILD.gn:17:1: whence it was imported. >> >> I suspect part of the problem may be that uname reports aarch64 instead >> of arm64? >> >> -- >> > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CAKSzg3TvQtRbqEC_e_FAAKW6m8bLkSAS2_Q9Pd%3DMcrjchw6Jfw%40mail.gmail.com.
