Open xuxin3101 opened 10 months ago
这个问题我通过将主目录的mm文件软链到msm-5.4文件夹里面解决了,但是仍然无法正常编译通过
这个问题我通过将主目录的mm文件软链到msm-5.4文件夹里面解决了,但是仍然无法正常编译通过
您好,请提供下编译报错的log,感谢。
这个问题我通过将主目录的mm文件软链到msm-5.4文件夹里面解决了,但是仍然无法正常编译通过
您好,请提供下编译报错的log,感谢。
使用的defconfig是从手机的/proc/config.gz中解压出来的
这是我使用的编译命令
make O=out ARCH=arm64 SUBARCH=arm64 CROSS_COMPILE=/data/www/custom_kernel/android_prebuilts_gcc_linux-x86_aarch64_aarch64-linux-android-4.9/bin/aarch64-linux-android- LLVM=1 CLANG_TRIPLE=aarch64-linux-gnu- CC=/data/www/custom_kernel/clang/bin/clang -j32
当我没有在vendor/msm-5.4中间建立软链的时候报这个错误 然后我建立软链,连接到源码下的mm文件夹
此时会报以下错误,我尝试修改源码,注释以下错误的代码,但是修改后依然编译不成功,还会有其他代码的报错,这让我怀疑是否不应该修改代码,是我的交叉编译工具链使用版本不对,还是说kernel不是软链到https://github.com/realme-kernel-opensource/realme_gt-AndroidT-vendor-source/tree/master/kernel 本文件中
这是clang版本
您好,请尝试使用开源代码中的 lahaina-qgki_defconfig文件作为defconfig。
您好,请尝试使用开源代码中的 lahaina-qgki_defconfig文件作为defconfig。
依然报错,
您好,请提供完整的编译log,感谢。
您好,请提供完整的编译log,感谢。
/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/Makefile:547: OPLUS_KASAN_TEST is /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/Makefile:598: TARGET_MEMLEAK_DETECT_TEST value is "" /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/Makefile:599: OPLUS_MEMLEAK_DETECT value is "" GEN Makefile ../drivers/power/Makefile:6: CALL ../scripts/atomic/check-atomics.sh CALL ../scripts/checksyscalls.sh CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o AR init/built-in.a ../drivers/power/Makefile:6: CHK kernel/kheaders_data.tar.xz CC drivers/soc/oplus/system/platform.o CC drivers/soc/oplus/system/slabtrace/slabtrace.o AR drivers/soc/oplus/system/slabtrace/built-in.a AR drivers/soc/oplus/system/built-in.a AR drivers/soc/built-in.a AR drivers/built-in.a GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o AR init/built-in.a LD vmlinux.o MODPOST vmlinux.o WARNING: vmlinux.o(.text+0x6c0340): Section mismatch in reference from the function update_manifest() to the variable .init.data:boot_command_line The function update_manifest() references the variable __initdata boot_command_line. This is often because update_manifest lacks a __initdata annotation or the annotation of boot_command_line is wrong.
WARNING: vmlinux.o(.text+0x6c0348): Section mismatch in reference from the function update_manifest() to the variable .init.data:boot_command_line The function update_manifest() references the variable __initdata boot_command_line. This is often because update_manifest lacks a __initdata annotation or the annotation of boot_command_line is wrong.
WARNING: vmlinux.o(.text+0x6c044c): Section mismatch in reference from the function update_telephony_manifest() to the variable .init.data:boot_command_line The function update_telephony_manifest() references the variable initdata boot_command_line. This is often because update_telephony_manifest lacks a initdata annotation or the annotation of boot_command_line is wrong.
WARNING: vmlinux.o(.text+0x6c0454): Section mismatch in reference from the function update_telephony_manifest() to the variable .init.data:boot_command_line The function update_telephony_manifest() references the variable initdata boot_command_line. This is often because update_telephony_manifest lacks a initdata annotation or the annotation of boot_command_line is wrong.
WARNING: "embms_tm_multicast_recv" [vmlinux] is a static EXPORT_SYMBOL
WARNING: "tsens_mtc_reset_history_counter" [vmlinux] is a static EXPORT_SYMBOL
MODINFO modules.builtin.modinfo
LD .tmp_vmlinux.kallsyms1
drivers/soc/oplus/system/theia/black_screen_check.o: In function black_screen_check_init': /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/soc/oplus/system/theia/black_screen_check.c:354: undefined reference to
msm_drm_register_client'
drivers/soc/oplus/system/theia/bright_screen_check.o: In function bright_screen_check_init': /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/soc/oplus/system/theia/bright_screen_check.c:414: undefined reference to
msm_drm_register_client'
drivers/soc/oplus/sensor/oplus_ssc_interact/oplus_ssc_interact.o: In function ssc_interactive_exit': /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/soc/oplus/sensor/oplus_ssc_interact/oplus_ssc_interact.c:543: undefined reference to
unregister_lcdinfo_notifier'
drivers/soc/oplus/sensor/oplus_ssc_interact/oplus_ssc_interact.o: In function ssc_interactive_init': /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/soc/oplus/sensor/oplus_ssc_interact/oplus_ssc_interact.c:499: undefined reference to
register_lcdinfo_notifier'
drivers/soc/oplus/sensor/oplus_sensor_feedback/sensor_feedback.o: In function sensor_sleep_ratio_init': /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/soc/oplus/sensor/oplus_sensor_feedback/sensor_feedback.c:907: undefined reference to
msm_drm_register_client'
drivers/soc/oplus/oplus_wakelock/oplus_wakelock_profiler.o: In function wakelock_statistics_function_init': /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/soc/oplus/oplus_wakelock/oplus_wakelock_profiler.c:654: undefined reference to
msm_drm_register_client'
drivers/block/zram/hybridswap/hybridswapd.o: In function swapd_init': /data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/block/zram/hybridswap/hybridswapd.c:1953: undefined reference to
msm_drm_register_client'
/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/block/zram/hybridswap/hybridswapd.c:1980: undefined reference to msm_drm_unregister_client' drivers/block/zram/hybridswap/hybridswapd.o: In function
swapd_exit':
/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/block/zram/hybridswap/hybridswapd.c:1992: undefined reference to msm_drm_unregister_client' drivers/input/oplus_fp_drivers/goodix_optical_fp/gf_spi.o: In function
gf_probe':
/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/input/oplus_fp_drivers/goodix_optical_fp/gf_spi.c:804: undefined reference to msm_drm_register_client' drivers/input/oplus_fp_drivers/anc_driver/jiiov_platform.o: In function
anc_probe':
/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/input/oplus_fp_drivers/anc_driver/jiiov_platform.c:1047: undefined reference to msm_drm_register_client' drivers/input/oplus_fp_drivers/anc_driver/jiiov_platform.o: In function
anc_remove':
/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/input/oplus_fp_drivers/anc_driver/jiiov_platform.c:1103: undefined reference to msm_drm_unregister_client' drivers/power/oplus/v1/oplus_charger.o: In function
oplus_chg_init':
/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out/../drivers/power/oplus/v1/oplus_charger.c:3410: undefined reference to `msm_drm_register_client'
make[1]: [/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/Makefile:1287: vmlinux] Error 1
make[1]: Leaving directory '/data/www/custom_kernel/realme_gt-AndroidT-kernel-source/out'
make: [Makefile:183: sub-make] Error 2
root@4cbb3e62353c:/data/www/custom_kernel/realme_gt-AndroidT-kernel-source#
哥,咋链接的
哥,咋链接的
软链 ln -s
然后我文件没问题了,还是报错../arch/arm64/include/asm/kgdb.h:21:25: error: value '1025' out of range for constraint 'I'
asm ("brk %0" : : "I" (KGDBCOMPILEDDBGBRKIMM));
^~~~~~~~~
../arch/arm64/include/asm/brk-imm.h:24:35: note: expanded from macro 'KGDBCOMPILEDDBGBRKIMM'
define KGDBCOMPILEDDBGBRKIMM 0x401
^~~~~
2 errors generated. HDRINST usr/include/linux/efsfssb.h make[2]: [../scripts/Makefile.build:109:arch/arm64/kernel/asm-offsets.s] 错误 1 make[1]: [/root/GT/realme_gt-AndroidT-kernel-source/Makefile:1323:prepare0] 错误 2 make[1]: *** 正在等待未完成的任务….
然后我文件没问题了,还是报错../arch/arm64/include/asm/kgdb.h:21:25: error: value '1025' out of range for constraint 'I' asm ("brk %0" : : "I" (KGDBCOMPILEDDBGBRKIMM)); ^
~~~~~~ ../arch/arm64/include/asm/brk-imm.h:24:35: note: expanded from macro 'KGDBCOMPILEDDBGBRKIMM' define KGDBCOMPILEDDBGBRKIMM 0x401 ^~~2 errors generated. HDRINST usr/include/linux/efsfssb.h make[2]: [../scripts/Makefile.build:109:arch/arm64/kernel/asm-offsets.s] 错误 1 make[1]: [/root/GT/realme_gt-AndroidT-kernel-source/Makefile:1323:prepare0] 错误 2 make[1]: *** 正在等待未完成的任务….
看起来像是编译工具的问题,我没有遇到这个问题。我应该是后面报错的
我现在的报错是这样的 GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o AR init/built-in.a LD vmlinux.o MODPOST vmlinux.o WARNING: vmlinux.o(.text+0x6c0340): Section mismatch in reference from the function update_manifest() to the variable .init.data:boot_command_line The function update_manifest() references the variable __initdata boot_command_line. This is often because update_manifest lacks a __initdata annotation or the annotation of boot_command_line is wrong.
WARNING: vmlinux.o(.text+0x6c0348): Section mismatch in reference from the function update_manifest() to the variable .init.data:boot_command_line The function update_manifest() references the variable __initdata boot_command_line. This is often because update_manifest lacks a __initdata annotation or the annotation of boot_command_line is wrong.
WARNING: vmlinux.o(.text+0x6c044c): Section mismatch in reference from the function update_telephony_manifest() to the variable .init.data:boot_command_line The function update_telephony_manifest() references the variable initdata boot_command_line. This is often because update_telephony_manifest lacks a initdata annotation or the annotation of boot_command_line is wrong.
WARNING: vmlinux.o(.text+0x6c0454): Section mismatch in reference from the function update_telephony_manifest() to the variable .init.data:boot_command_line The function update_telephony_manifest() references the variable initdata boot_command_line. This is often because update_telephony_manifest lacks a initdata annotation or the annotation of boot_command_line is wrong.
FATAL: modpost: Section mismatches detected. Set CONFIG_SECTION_MISMATCH_WARN_ONLY=y to allow them. make[2]: [../scripts/Makefile.modpost:66: __modpost] Error 1 make[1]: [/root/GT/realme_gt-AndroidT-kernel-source/Makefile:1287: vmlinux] Error 2 make[1]: Leaving directory '/root/GT/realme_gt-AndroidT-kernel-source/out' make: *** [Makefile:183: sub-make] Error 2 ![Uploading 90F2CC05E16335EDDE66BF45358B36A7.png…]()
现在的抱错是这样 WARNING: "embms_tm_multicast_recv" [vmlinux] is a static EXPORT_SYMBOL WARNING: "tsens_mtc_reset_history_counter" [vmlinux] is a static EXPORT_SYMBOL MODINFO modules.builtin.modinfo LD .tmp_vmlinux.kallsyms1 ld.lld: error: undefined symbol: register_lcdinfo_notifier
referenced by oplus_ssc_interact.c:499 (../drivers/soc/oplus/sensor/oplus_ssc_interact/oplus_ssc_interact.c:499) vmlinux.o:(ssc_interactive_init$071918af4f7bdbf03960aef165a4c2e3)
ld.lld: error: undefined symbol: msm_drm_register_client
referenced by oplus_wakelock_profiler.c:654 (../drivers/soc/oplus/oplus_wakelock/oplus_wakelock_profiler.c:654) vmlinux.o:(wakelock_statistics_function_init) referenced by black_screen_check.c:354 (../drivers/soc/oplus/system/theia/black_screen_check.c:354) vmlinux.o:(black_screen_check_init) referenced by bright_screen_check.c:414 (../drivers/soc/oplus/system/theia/bright_screen_check.c:414) vmlinux.o:(bright_screen_check_init) referenced by sensor_feedback.c:907 (../drivers/soc/oplus/sensor/oplus_sensor_feedback/sensor_feedback.c:907) vmlinux.o:(sensor_feedback_probe$fc62dfce90a80fd370db405577e132c6) referenced by hybridswapd.c:1953 (../drivers/block/zram/hybridswap/hybridswapd.c:1953) vmlinux.o:(swapd_init) referenced by gf_spi.c:804 (../drivers/input/oplus_fp_drivers/goodix_optical_fp/gf_spi.c:804) vmlinux.o:(gf_probe$3ba3ea43c4f36a37c2f3fc7ba711363e) referenced by jiiov_platform.c:1047 (../drivers/input/oplus_fp_drivers/anc_driver/jiiov_platform.c:1047) vmlinux.o:(anc_probe$b8be876cc5b14b119cf1484d006c3dbe) referenced by oplus_charger.c:3410 (../drivers/power/oplus/v1/oplus_charger.c:3410) vmlinux.o:(oplus_chg_init)
ld.lld: error: undefined symbol: unregister_lcdinfo_notifier
referenced by oplus_ssc_interact.c:543 (../drivers/soc/oplus/sensor/oplus_ssc_interact/oplus_ssc_interact.c:543) vmlinux.o:(ssc_interactive_exit$071918af4f7bdbf03960aef165a4c2e3)
ld.lld: error: undefined symbol: msm_drm_unregister_client
referenced by hybridswapd.c:1980 (../drivers/block/zram/hybridswap/hybridswapd.c:1980) vmlinux.o:(swapd_init) referenced by hybridswapd.c:1992 (../drivers/block/zram/hybridswap/hybridswapd.c:1992) vmlinux.o:(swapd_exit) referenced by jiiov_platform.c:1103 (../drivers/input/oplus_fp_drivers/anc_driver/jiiov_platform.c:1103) vmlinux.o:(anc_remove$b8be876cc5b14b119cf1484d006c3dbe) make[1]: *** [/root/GT/realme_gt-AndroidT-kernel-source/Makefile:1288: vmlinux] Error 1 make[1]: Leaving directory '/root/GT/realme_gt-AndroidT-kernel-source/out'
现在的抱错是这样 WARNING: "embms_tm_multicast_recv" [vmlinux] is a static EXPORT_SYMBOL WARNING: "tsens_mtc_reset_history_counter" [vmlinux] is a static EXPORT_SYMBOL MODINFO modules.builtin.modinfo LD .tmp_vmlinux.kallsyms1 ld.lld: error: undefined symbol: register_lcdinfo_notifier
referenced by oplus_ssc_interact.c:499 (../drivers/soc/oplus/sensor/oplus_ssc_interact/oplus_ssc_interact.c:499) vmlinux.o:(ssc_interactive_init$071918af4f7bdbf03960aef165a4c2e3)
ld.lld: error: undefined symbol: msm_drm_register_client
referenced by oplus_wakelock_profiler.c:654 (../drivers/soc/oplus/oplus_wakelock/oplus_wakelock_profiler.c:654) vmlinux.o:(wakelock_statistics_function_init) referenced by black_screen_check.c:354 (../drivers/soc/oplus/system/theia/black_screen_check.c:354) vmlinux.o:(black_screen_check_init) referenced by bright_screen_check.c:414 (../drivers/soc/oplus/system/theia/bright_screen_check.c:414) vmlinux.o:(bright_screen_check_init) referenced by sensor_feedback.c:907 (../drivers/soc/oplus/sensor/oplus_sensor_feedback/sensor_feedback.c:907) vmlinux.o:(sensor_feedback_probe$fc62dfce90a80fd370db405577e132c6) referenced by hybridswapd.c:1953 (../drivers/block/zram/hybridswap/hybridswapd.c:1953) vmlinux.o:(swapd_init) referenced by gf_spi.c:804 (../drivers/input/oplus_fp_drivers/goodix_optical_fp/gf_spi.c:804) vmlinux.o:(gf_probe$3ba3ea43c4f36a37c2f3fc7ba711363e) referenced by jiiov_platform.c:1047 (../drivers/input/oplus_fp_drivers/anc_driver/jiiov_platform.c:1047) vmlinux.o:(anc_probe$b8be876cc5b14b119cf1484d006c3dbe) referenced by oplus_charger.c:3410 (../drivers/power/oplus/v1/oplus_charger.c:3410) vmlinux.o:(oplus_chg_init)
ld.lld: error: undefined symbol: unregister_lcdinfo_notifier
referenced by oplus_ssc_interact.c:543 (../drivers/soc/oplus/sensor/oplus_ssc_interact/oplus_ssc_interact.c:543) vmlinux.o:(ssc_interactive_exit$071918af4f7bdbf03960aef165a4c2e3)
ld.lld: error: undefined symbol: msm_drm_unregister_client
referenced by hybridswapd.c:1980 (../drivers/block/zram/hybridswap/hybridswapd.c:1980) vmlinux.o:(swapd_init) referenced by hybridswapd.c:1992 (../drivers/block/zram/hybridswap/hybridswapd.c:1992) vmlinux.o:(swapd_exit) referenced by jiiov_platform.c:1103 (../drivers/input/oplus_fp_drivers/anc_driver/jiiov_platform.c:1103) vmlinux.o:(anc_remove$b8be876cc5b14b119cf1484d006c3dbe) make[1]: *** [/root/GT/realme_gt-AndroidT-kernel-source/Makefile:1288: vmlinux] Error 1 make[1]: Leaving directory '/root/GT/realme_gt-AndroidT-kernel-source/out'
跟我的报错好像差不多,留个联系方式,我私你讨论下
QQ?3200085060
您好,请参考下面的方法进行编译,感谢。 https://github.com/realme-kernel-opensource/realme_gt-AndroidT-kernel-source 是编译kernel 主目录,代码下载后最好重命名为kernel/msm-5.4/xxx(kernel code),这样的目录结构,然后将vendor source的代码 kernel部分按目录名称拷贝到对应kernel source主目录,vendor目录部分和kernel目录放在同一级目录下。 当前贴出的报错缺少依赖都是kernel/msm-5.4/techpack 中的,请将vendor source中的 kernel/msm-5.4/techpack 拷贝或链接到kernel主目录下。
您好,请参考下面的方法进行编译,感谢。 https://github.com/realme-kernel-opensource/realme_gt-AndroidT-kernel-source 是编译kernel 主目录,代码下载后最好重命名为kernel/msm-5.4/xxx(kernel code),这样的目录结构,然后将vendor source的代码 kernel部分按目录名称拷贝到对应kernel source主目录,vendor目录部分和kernel目录放在同一级目录下。 当前贴出的报错缺少依赖都是kernel/msm-5.4/techpack 中的,请将vendor source中的 kernel/msm-5.4/techpack 拷贝或链接到kernel主目录下。
我使用以下脚本处理,可以成功编译,但是编译的文件大小为42m,我从手机里面解出来的kernel是46m,而且刷入后也无法开机。请问是什么问题
git clone https://github.com/realme-kernel-opensource/realme_gt-AndroidT-vendor-source.git
cd realme_gt-AndroidT-vendor-source/kernel/msm-5.4
git clone https://github.com/realme-kernel-opensource/realme_gt-AndroidT-kernel-source.git
mv techpack techpack_backup
mv realme_gt-AndroidT-kernel-source/* ./
rm -rf realme_gt-AndroidT-kernel-source
mv techpack_backup/* ./techpack/
rm -rf techpack_backup/
export PATH=/data/www/custom_kernel/clang/bin:$PATH
export MAKE_PATH=/data/www/custom_kernel/build-tools/linux-x86/bin/
export CROSS_COMPILE=/data/www/custom_kernel/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export KERNEL_ARCH=arm64
export CLANG_TRIPLE=aarch64-linux-gnu-
export ARCH=${KERNEL_ARCH}
export TARGET_INCLUDES=${TARGET_KERNEL_MAKE_CFLAGS}
export TARGET_LINCLUDES=${TARGET_KERNEL_MAKE_LDFLAGS}
TARGET_KERNEL_MAKE_ENV="HOSTCC=/data/www/custom_kernel/clang/bin/clang "
TARGET_KERNEL_MAKE_ENV+="CC=/data/www/custom_kernel/clang/bin/clang "
TARGET_KERNEL_MAKE_ENV+="LLVM=/data/www/custom_kernel/clang/bin/clang"
export TARGET_KERNEL_MAKE_ENV
${MAKE_PATH}make O=out clean &&${MAKE_PATH}make O=out mrproper
${MAKE_PATH}make O=out ${TARGET_KERNEL_MAKE_ENV} HOSTLDFLAGS="${TARGET_LINCLUDES}" ARCH=${ARCH} CROSS_COMPILE=${CROSS_COMPILE} vendor/lahaina-qgki_defconfig
${MAKE_PATH}make ARCH=${ARCH} CROSS_COMPILE=${CROSS_COMPILE} HOSTCFLAGS="${TARGET_INCLUDES}" HOSTLDFLAGS="${TARGET_LINCLUDES}" O=out ${TARGET_KERNEL_MAKE_ENV} -j12
编译结束后是这样的
您好,请参考下面的方法进行编译,感谢。https://github.com/realme-kernel-opensource/realme_gt-AndroidT-kernel-source 是编译kernel 主目录,代码下载后最好重命名为kernel/msm-5.4/xxx(kernel code),这样的目录结构,然后将vendor source的代码 kernel部分按目录名称拷贝到对应的kernel source主目录,vendor目录部分和kernel目录放在同一级目录下。当前贴出的报错缺少依赖都是kernel/msm-5.4/techpack 中的,请将vendor source中的 kernel/msm-5.4/techpack 拷贝或链接到kernel主目录下。
我使用以下脚本处理,可以成功编译,但是编译的文件大小为42m,我从手机里面解出来的kernel是46m,而且刷入后也无法开机。请问是什么问题
git clone https://github.com/realme-kernel-opensource/realme_gt-AndroidT-vendor-source.git cd realme_gt-AndroidT-vendor-source/kernel/msm-5.4 git clone https://github.com/realme-kernel-opensource/realme_gt-AndroidT-kernel-source.git mv techpack techpack_backup mv realme_gt-AndroidT-kernel-source/* ./ rm -rf realme_gt-AndroidT-kernel-source mv techpack_backup/* ./techpack/ rm -rf techpack_backup/ export PATH=/data/www/custom_kernel/clang/bin:$PATH export MAKE_PATH=/data/www/custom_kernel/build-tools/linux-x86/bin/ export CROSS_COMPILE=/data/www/custom_kernel/aarch64-linux-android-4.9/bin/aarch64-linux-android- export KERNEL_ARCH=arm64 export CLANG_TRIPLE=aarch64-linux-gnu- export ARCH=${KERNEL_ARCH} export TARGET_INCLUDES=${TARGET_KERNEL_MAKE_CFLAGS} export TARGET_LINCLUDES=${TARGET_KERNEL_MAKE_LDFLAGS} TARGET_KERNEL_MAKE_ENV="HOSTCC=/data/www/custom_kernel/clang/bin/clang " TARGET_KERNEL_MAKE_ENV+="CC=/data/www/custom_kernel/clang/bin/clang " TARGET_KERNEL_MAKE_ENV+="LLVM=/data/www/custom_kernel/clang/bin/clang" export TARGET_KERNEL_MAKE_ENV ${MAKE_PATH}make O=out clean &&${MAKE_PATH}make O=out mrproper ${MAKE_PATH}make O=out ${TARGET_KERNEL_MAKE_ENV} HOSTLDFLAGS="${TARGET_LINCLUDES}" ARCH=${ARCH} CROSS_COMPILE=${CROSS_COMPILE} vendor/lahaina-qgki_defconfig ${MAKE_PATH}make ARCH=${ARCH} CROSS_COMPILE=${CROSS_COMPILE} HOSTCFLAGS="${TARGET_INCLUDES}" HOSTLDFLAGS="${TARGET_LINCLUDES}" O=out ${TARGET_KERNEL_MAKE_ENV} -j12
编译结束后是这样的
怎么解决的我也卡这里了
In file included from ../drivers/soc/oplus/system/slabtrace/slabtrace.c:10: ../drivers/soc/oplus/system/slabtrace/slabtrace.h:33:10: fatal error: '../../../../kernel/msm-5.4/mm/internal.h' file not found
include <../../../../kernel/msm-5.4/mm/internal.h>
1 error generated.
缺少kernel/5.4/mm文件,kernel是软链的vendor中的文件,对应的vendor中并没有发现这个文件 https://github.com/realme-kernel-opensource/realme_gt-AndroidT-vendor-source/tree/master/kernel 请问这个应该如何处理,从哪里补齐缺少的文件