You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[deps/zlib] Android arm64 build fails due to missing cpufeatures library #46749
changed the title [-]Android arm64 build fails due to missing cpufeatures library[/-][+][deps/zlib] Android arm64 build fails due to missing cpufeatures library[/+]on Feb 20, 2023
I don't really have a suggestion on how to fix that except by vendoring it and the other files except Android.mk in that directory. PR or better solution welcome, I'd say.
@bnoordhuis My proposal would be to source it locally from $ANDROID_NDK_ROOT/sources/android/cpufeatures. I am not aware how to acces ENV variables in the gyp file though.
@bnoordhuis If it does not cause legal issues I think vendoring would be the most stable option indeed. The library itself seems deprecated anyways so I would not expect updates either. For me it is not quite clear how v8 sources it though, because it is not committed there either. Is the build system downloading it or how does it work with v8 deps?
Activity
[-]Android arm64 build fails due to missing cpufeatures library[/-][+][deps/zlib] Android arm64 build fails due to missing cpufeatures library[/+]nappy commentedon Feb 20, 2023
I think this part of
BUILD.gnis missing in the corresponding gyp file:bnoordhuis commentedon Feb 20, 2023
V8 basically slurps in this file: https://chromium.googlesource.com/android_ndk/+/refs/heads/main/sources/android/cpufeatures/cpu-features.c
I don't really have a suggestion on how to fix that except by vendoring it and the other files except Android.mk in that directory. PR or better solution welcome, I'd say.
nappy commentedon Feb 21, 2023
@bnoordhuis My proposal would be to source it locally from $ANDROID_NDK_ROOT/sources/android/cpufeatures. I am not aware how to acces ENV variables in the gyp file though.
bnoordhuis commentedon Feb 21, 2023
You can't access them directly but you can from configure.py, which then writes config.gypi.
However, that adds one more moving part to the build and moving parts have a tendency to break down, hence my suggestion of vendoring.
That file seems to change only very infrequently; last two changes were 2 and 5 years ago, respectively.
richardlau commentedon Feb 21, 2023
FWIW
android_configure.pyalready knows the path to the Android NDK:node/android_configure.py
Lines 25 to 33 in 254574e
nappy commentedon Feb 21, 2023
@bnoordhuis If it does not cause legal issues I think vendoring would be the most stable option indeed. The library itself seems deprecated anyways so I would not expect updates either. For me it is not quite clear how v8 sources it though, because it is not committed there either. Is the build system downloading it or how does it work with v8 deps?
bnoordhuis commentedon Feb 21, 2023
Yes, chromium's fetch tool downloads it when you clone the v8 repo.
bnoordhuis commentedon Mar 21, 2023
@nappy do you want to send a pull request or can I close this?