Unable to build busybox while it refers to some platform related header files

I was trying to build my own rootfs using busybox souce code,and the version is 1.24.2,but something went wrong with my build tools

In file included from /home/hcyan/tools/cc/R24.1/gcc-linaro-5.2-2015.11-x86_64_aarch64-linux-gnu/lib/gcc/aarch64-linux-gnu/5.2.1/include-fixed/syslimits.h:7:0,
from /home/hcyan/tools/cc/R24.1/gcc-linaro-5.2-2015.11-x86_64_aarch64-linux-gnu/lib/gcc/aarch64-linux-gnu/5.2.1/include-fixed/limits.h:34,
from include/platform.h:141,
from include/libbb.h:13,
from include/busybox.h:8,
from applets/applets.c:9:
/home/hcyan/tools/cc/R24.1/gcc-linaro-5.2-2015.11-x86_64_aarch64-linux-gnu/lib/gcc/aarch64-linux-gnu/5.2.1/include-fixed/limits.h:168:61: fatal error: limits.h: No such file or directory
compilation terminated.
scripts/Makefile.build:197: recipe for target ‘applets/applets.o’ failed
make[1]: *** [applets/applets.o] Error 1
Makefile:372: recipe for target ‘applets_dir’ failed
make: *** [applets_dir] Error 2

I do know the file limits.h exits in the path:

And the limits.h is included by syslimits.h like this: #include_next <limits.h>
what is wrong with my build tools?

Look at the actual error, it wants a specific location to have limits.h:

/home/hcyan/tools/cc/R24.1/gcc-linaro-5.2-2015.11-x86_64_aarch64-linux-gnu/lib/gcc/aarch64-linux-gnu/5.2.1/include-fixed/limits.h:168:61: fatal error: limits.h: No such file or directory

I assume you are cross compiling, in which case it looks at the specific architecture version of files. You wouldn’t want it to find “/usr/include” if your host is x86_64 and cross compile is for aarch64. If you are compiling directly on the Jetson, that’s a different story, and you would want it to find the “/usr/include” version. Which one it finds depends on a combination of the “-I” list of search locations and the syntax used for the include, i.e.:

#include <limits.h>
// or
#include "some/path/limits.h"

Are you cross compiling, or are you compiling natively? Back track the list of headers and find the original include statement…what syntax was used for that?