[Android][v8] V8 14.3.92 compilation fails with missing libc++ forward headers (__fwd/byte.h)

8 views
Skip to first unread message

何浩

unread,
Nov 11, 2025, 6:37:27 AM (5 days ago) Nov 11
to v8-dev

I'm using GitHub Actions to compile Android V8 static libraries (arm/arm64/x64) on Ubuntu, but the compilation keeps failing.

Error Log
```
While building module 'std_core':
  In file included from <module-includes>:1:
  gen/third_party/libc++/src/include/__cstddef/byte.h:13:10: fatal error: '__fwd/byte.h' file not found
     13 | #include <__fwd/byte.h>
        |          ^~~~~~~~~~~~~~
  1 error generated.
  [1150/4208] CXX clang_x64_v8_arm64/obj/buildtools/third_party/libc++abi/libc++abi/stdlib_exception.o
  [1151/4208] CXX clang_x64_v8_arm64/obj/buildtools/third_party/libc++abi/libc++abi/fallback_malloc.o


```
GN Configuration:
```
target_os="android"
target_cpu="arm64"
v8_target_cpu="arm64"
clang_use_chrome_plugins=false
chrome_pgo_phase=false
dcheck_always_on=false
enable_rust=false
is_cfi=false
is_asan=false
is_clang=true
is_component_build=false
is_debug=false
strip_debug_info=true
symbol_level=0
treat_warnings_as_errors=false
use_custom_libcxx=false
use_rtti=false
use_custom_libunwind=false
use_ml_inliner=false
v8_deprecation_warnings=false
v8_enable_builtins_optimization=false
v8_enable_gdbjit=false
v8_enable_i18n_support=false
v8_enable_pointer_compression=false
v8_enable_sandbox=false
v8_enable_snapshot_compression=false
v8_enable_temporal_support=false
v8_enable_test_features=false
v8_enable_fuzztest=false
v8_enable_webassembly=true
v8_imminent_deprecation_warnings=false
v8_monolithic=true
v8_use_external_startup_data=false
```

v8 version:  14.3.92/14.3.127


- If I set `use_custom_libcxx=true`, it compiles successfully, but crashes when running on Android devices
- I tried setting `android_ndk_root="${NDK_ROOT}"` and `clang_base_path="${NDK_ROOT}/toolchains/llvm/prebuilt/linux-x86_64"`, but the compilation still fails
- My GitHub Actions repository URL: https://github.com/haroel/v8-build

Could you please help me identify what is configured incorrectly?

Reply all
Reply to author
Forward
0 new messages