Android AOSP构建失败-ckati失败，退出状态1

所以我一直在努力构建Android AOSP项目。我遵循了官方文件的指导方针（）。 在几次尝试之后，我总是从终端获得下面的错误堆栈跟踪。我正在尝试构建“aosp\u coral-userdebug”。我注意到的另一件事是，如果我使用菜单中的另一个组合，我也会得到另一种形式的“忍者”错误。 请帮忙

12:09:31 You are building on a machine with 15.4GB of RAM
12:09:31 
12:09:31 The minimum required amount of free memory is around 16GB,
12:09:31 and even with that, some configurations may not work.
12:09:31 
12:09:31 If you run into segfaults or other errors, try reducing your
12:09:31 -j value.
12:09:31 ************************************************************
============================================
PLATFORM_VERSION_CODENAME=S
PLATFORM_VERSION=S
TARGET_PRODUCT=aosp_coral
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-47-generic-x86_64-Ubuntu-18.04.5-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=AOSP.MASTER
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=hardware/google/av hardware/google/camera hardware/google/interfaces hardware/google/pixel device/google/coral hardware/qcom/sm8150/display hardware/qcom/sm8150/data/ipacfg-mgr hardware/qcom/sm8150/gps vendor/google/airbrush/floral vendor/google/biometrics/face vendor/google/camera vendor/google/darwinn vendor/qcom/sm8150 vendor/qcom/sm8150/proprietary/commonsys/telephony-apps/DataStatusNotification vendor/qcom/sm8150/proprietary/data/permissions vendor/qcom/sm8150/proprietary/gps vendor/qcom/sm8150/codeaurora/location vendor/google/interfaces vendor/qcom/sensors vendor/google/tools/sensors vendor/qcom/sm7250/codeaurora/commonsys/telephony/ims/ims-ext-common vendor/qcom/sm7250/codeaurora/dataservices/rmnetctl vendor/qcom/sm7250/proprietary/commonsys/qcrilOemHook vendor/qcom/sm7250/proprietary/commonsys/telephony-apps/ims vendor/qcom/sm7250/proprietary/commonsys/telephony-apps/QtiTelephonyService vendor/qcom/sm7250/proprietary/commonsys/telephony-apps/xdivert vendor/qcom/sm7250/proprietary/qcril-data-hal vendor/qcom/sm7250/proprietary/qcril-hal
============================================
wildcard(out/target/product/coral/clean_steps.mk) was changed, regenerating...
[ 99% 1236/1237] finishing build rules ...
FAILED: 
build/make/core/main.mk:1336: warning:  device/google/coral/aosp_coral.mk produces files inside build/make/target/product/generic_system.mks artifact path requirement. 
Offending entries:
system/etc/permissions/com.qti.snapdragon.sdk.display.xml
system/framework/com.qti.snapdragon.sdk.display.jar
system/framework/com.qualcomm.qti.uceservice-V2.0-java.jar
system/framework/vendor.qti.hardware.alarm-V1.0-java.jar
system/framework/vendor.qti.hardware.data.latency-V1.0-java.jar
system/framework/vendor.qti.hardware.factory-V1.0-java.jar
system/framework/vendor.qti.ims.callinfo-V1.0-java.jar
system/framework/vendor.qti.voiceprint-V1.0-java.jar
system/lib/libDiagService.so
system/lib/libOpenCL_system.so
system/lib/libadsprpc_system.so
system/lib/libcdsprpc_system.so
system/lib/libdiag_system.so
system/lib/libdisplayconfig.so
system/lib/libmdsprpc_system.so
system/lib/libmmosal.so
system/lib/libqmi_cci_system.so
system/lib/libsdsprpc_system.so
system/lib64/libDiagService.so
system/lib64/libOpenCL_system.so
system/lib64/libadsprpc_system.so
system/lib64/libcdsprpc_system.so
system/lib64/libdiag_system.so
system/lib64/libdisplayconfig.so
system/lib64/libmdsprpc_system.so
system/lib64/libmmosal.so
system/lib64/libqmi_cci_system.so
system/lib64/libsdsprpc_system.so
build/make/core/main.mk:1336: error: Build failed.
12:10:42 ckati failed with: exit status 1

#### failed to build some targets (02:25 (mm:ss)) ####```

---

此错误通常意味着由于没有剩余RAM，构建过程被笔记本电脑中的操作系统终止。 您可以通过在错误发生后运行dmesg并在内核日志中看到您的进程被终止来确认

解决办法是：

使用小于当前使用的j值运行make，或

获取更多内存，或者

添加交换空间（将用作虚拟内存的磁盘部分）

---

您正在构建一台具有15.4GB RAM的机器。所需的最小可用内存量约为16GB，即使如此，某些配置也可能无法工作。如果遇到SEGFULTS或其他错误，请尝试减小-j值。如果我的构建过程从这个开始，我会先购买RAM。。即使它因缺少分号而失败。是的，长期来看，最好是增加内存。短期而言，其他两种解决方案中的任何一种都应该解决这个问题。日志开头的警告似乎相当严重。为什么不在低并行性（较低的

j

value）或云中的大型VM中运行构建？