Appears when pakcage is compiled fatal error: gc_vip_kernel_pm.h: No such file or directory

bsp/drivers/npu/aw_nna_vip/gc_vip_kernel.c:55:10: fatal error: gc_vip_kernel_pm.h: No such file or directory
55 | #include <gc_vip_kernel_pm.h>
| ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
scripts/Makefile.build:289: recipe for target 'bsp/drivers/npu/aw_nna_vip/gc_vip_kernel.o' failed
make[7]: *** [bsp/drivers/npu/aw_nna_vip/gc_vip_kernel.o] Error 1
scripts/Makefile.build:552: recipe for target 'bsp/drivers/npu/aw_nna_vip' failed
make[6]: *** [bsp/drivers/npu/aw_nna_vip] Error 2
scripts/Makefile.build:552: recipe for target 'bsp/drivers/npu' failed
make[5]: *** [bsp/drivers/npu] Error 2
scripts/Makefile.build:552: recipe for target 'bsp/drivers' failed
make[4]: *** [bsp/drivers] Error 2
Makefile:1910: recipe for target 'bsp' failed
make[3]: *** [bsp] Error 2
make[3]: Leaving directory '/home/lmmuyu/Linux/OpenWrt/build_dir/target-arm_cortex-a7+neon-vfpv4_musl_eabi/linux-yuzukihd_v851se/linux-5.15.138'
Makefile:52: recipe for target '/home/lmmuyu/Linux/OpenWrt/build_dir/target-arm_cortex-a7+neon-vfpv4_musl_eabi/linux-yuzukihd_v851se/helloworld/.built' failed
make[2]: *** [/home/lmmuyu/Linux/OpenWrt/build_dir/target-arm_cortex-a7+neon-vfpv4_musl_eabi/linux-yuzukihd_v851se/helloworld/.built] Error 2
make[2]: Leaving directory '/home/lmmuyu/Linux/OpenWrt/package/kernel/hellowold'
time: package/kernel/hellowold/compile#65.57#9.10#75.38
ERROR: package/kernel/hellowold failed to build.
package/Makefile:126: recipe for target 'package/kernel/hellowold/compile' failed
make[1]: *** [package/kernel/hellowold/compile] Error 1
make[1]: Leaving directory '/home/lmmuyu/Linux/OpenWrt'
/home/lmmuyu/Linux/OpenWrt/include/toplevel.mk:230: recipe for target 'package/kernel/hellowold/compile' failed
make: *** [package/kernel/hellowold/compile] Error 2

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

Okay, thank you.