编译Android 15(Cuttlefish)内核时ABI符号缺失的解决求助
Android 15(Cuttlefish)内核编译ABI检查错误求助
我在Android 15(Cuttlefish)环境下测试新的驱动补丁,编译内核时遇到ABI检查错误,提示大量符号缺失。我尝试了以下方法但均未解决问题:
- 新增符号文件
common/android/abi_gki_aarch64_mydriver,修改bazel-android-kernel/common/BUILD.bazel将该文件与其他abi_gki_aarch64文件一同列出,执行tools/bazel run //common:kernel_aarch64_abi_update,仍报错。 - 试图通过设置
define_abi_targets=False关闭ABI检查,但未找到BUILD.bazel中的对应配置位置。 - 直接将新增符号添加至
common/android/abi_gki_aarch64,无效。 - 执行
tools/bazel run //common:kernel_aarch64_abi_update_symbol_list,也无济于事。
错误日志如下:
$ tools/bazel run //common:kernel_aarch64_abi_update Starting local Bazel server and connecting to it... INFO: Analyzed target //common:kernel_aarch64_abi_update (62 packages loaded, 98417 targets configured). ERROR: /path/to/android-kernel/common/BUILD.bazel:149:22: Checking for kmi_symbol_list_strict_mode (lto=default;trim) @@//common:kernel_aarch64 failed: (Exit 1): bash failed: error executing KernelBuildKmiSymbolListStrictMode command (from target //common:kernel_aarch64) /bin/bash -c ... (remaining 1 argument skipped) Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging Symbols missing from the ksymtab: >>LONG LIST OF SYMBOLS<< Target //common:kernel_aarch64_abi_update failed to build Use --verbose_failures to see the command lines of failed build steps. INFO: Elapsed time: 9.502s, Critical Path: 1.72s INFO: 4 processes: 4 internal. ERROR: Build did NOT complete successfully ERROR: Build failed. Not running target
内容的提问来源于stack exchange,提问作者user1412028
相关产品推荐
相关产品推荐

