Building on AArch64 Linux

[Sam Parker-Haynes]

Hi,

Something has happened in the last 2-3 weeks which means I can no longer build V8 on aarch64 linux. There is a x86-64 binary in my tree third_party/llvm-libclang/lib/libclang.so. Is this an issue with 'metagen'? I've seen this may have been fixed for other platforms here: https://chromium-review.googlesource.com/c/v8/v8/+/8322487.

Is there something we can do to enable native builds again?

Thanks,

Sam

[Matthias Liedtke]

Hi Sam,

Yes, this is an issue with metagen, I have filed an issue for it since we have a few internal cases where we build on Linux arm64 as well: https://crbug.com/555796819.

Unfortunately, our CI+CQ pipeline does not do this and always cross-compiles which is why this issue was only flushed out reasonably late.

IIRC, these changes were reverted because they caused issues on the Chromium side, I don't know whether they have been relanded in the meantime.

Could you try adding

v8_use_metagen_instance_types = false

as a workaround to your args.gn?

- Matthias

--
--
v8-dev mailing list
v8-...@googlegroups.com
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 v8-dev+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/v8-dev/e9bbc6a1-a585-4352-99bd-7f93f02101d4n%40googlegroups.com.

--

Matthias Liedtke

Software Engineer

mlie...@google.com

Google Germany GmbH

Erika-Mann-Straße 33

80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail an die falsche Person gesendet wurde. 

     

This e-mail is confidential. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person.

[Jakob Gruber]

Hi,

yes - the cl you linked is exactly right. See also https://issues.chromium.org/issues/555796819 for more related discussions.

The short version: chromium and v8 unconditionally treats a host_os == "linux" as x64 in several clang-related packages, including libclang. The CL you found is a way to work around this medium- to long-term. Do let me know if you run into any issues.

I wouldn't recommend sticking with torque; the torque fallback mechanism is not intended to stay post-transition period. 

Cheers, 

Jakob

On Tue, Sep 8, 2026 at 12:13 PM Sam Parker-Haynes <sam.p...@arm.com> wrote:

--

[Sam Parker-Haynes]

Okay, thanks both.

v8_use_metagen_instance_types = false is working for me, so that's good enough for now.

Cheers!