Where is your arm eabi cross tool chain at? When you specify “arm”, then you also must specify the tool chain which works with this. I am using Fedora, and so I have different tools than you will, but this works for me:
make <b>ARCH=arm CROSS_COMPILE=/usr/local/arm-linux-gnueabihf/gcc-linaro-5.3-2016.02/bin/arm-linux-gnueabihf-</b> p2771-0000-500_defconfig
Note that on my system I have this directory:
Within this directory is a complete set of armhf EABI tools. All tools within this begin with the name:
If I prefix this to “gcc”, which is what the compile does as it runs when those environment variables are present, this what would occur (which is conveniently the full path to the gcc compiler dedicated to running on a PC with output of arm gnueabi output):
Depending on what was installed for your host on your PC you might have this content (although it would be in a different location…I have maybe a dozen cross tool chains which are not part of Fedora’s distribution).
Cross compiling is different than native compile since your build will normally assume you are building for your own system. As soon as the target is a different computer you must also specify both the architecture and where to find the tools capable of output of that architecture.
NOTE: If you were to run this compile directly on the TX2, then you would perhaps still need to do this. The reason is that gnueabi is a 32-bit subset of the TX2’s architecture. The normal tool support on a TX2 is 64-bit, arm64. However, far more cross tools exist on a PC than exist on arm64.