Hi Experts, I really need some help please. Here is the result of my first build attempt on a tree made from pristine Linux 5.2.21 and the corresponding RT patch, which applied cleanly: $ /i/runtime/arm64/kernel/build-arm64-rt.sh make[1]: Entering directory '/ssd/build/linux-5.2.y' GEN Makefile scripts/kconfig/conf --syncconfig Kconfig GEN Makefile Using /ssd/linux-5.2.y as source for kernel CALL /ssd/linux-5.2.y/scripts/atomic/check-atomics.sh CALL /ssd/linux-5.2.y/scripts/checksyscalls.sh CHK include/generated/compile.h GZIP kernel/config_data.gz CC kernel/configs.o AR kernel/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 MODINFO modules.builtin.modinfo kernel/sched/core.o: In function `migrate_enable': core.c:(.text+0x3750): undefined reference to `takedown_cpu_task' core.c:(.text+0x3750): relocation truncated to fit: R_AARCH64_ADR_PREL_PG_HI21 against undefined symbol `takedown_cpu_task' core.c:(.text+0x3754): undefined reference to `takedown_cpu_task' /ssd/linux-5.2.y/Makefile:1054: recipe for target 'vmlinux' failed make[1]: *** [vmlinux] Error 1 make[1]: Leaving directory '/ssd/build/linux-5.2.y' Makefile:179: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 Am I right to think that this pointer, takedown_cpu_task, is more that some maximum distance away from object file "core.o" in the link image for the build setup? How are other globals avoiding this same problem, what't the best fix? Thanks much, Dick
