Actions
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 355 subscribers
  • Views 197 views
  • Users 0 members are here
Related

cannot create uImage

Former Member

root@gaurav-desktop:~/scratch/BuildZynq/linux-xlnx-xilinx-v14.7# make -j ARCH=arm UIMAGE_LOADADDR=0x8000 uImage
  CHK     include/generated/uapi/linux/version.h
  CC      scripts/mod/empty.o
  CC      scripts/mod/devicetable-offsets.s
cc1: error: unrecognized command line option u2018-mlittle-endianu2019
cc1: error: unrecognized command line option u2018-mno-thumb-interworku2019
scripts/mod/empty.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
scripts/mod/empty.c:1:0: error: bad value (armv5t) for -march= switch
make[2]: *** [scripts/mod/empty.o] Error 1
make[2]: *** Waiting for unfinished jobs....
cc1: error: unrecognized command line option u2018-mlittle-endianu2019
cc1: error: unrecognized command line option u2018-mno-thumb-interworku2019
scripts/mod/devicetable-offsets.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
scripts/mod/devicetable-offsets.c:1:0: error: bad value (armv5t) for -march= switch
make[2]: *** [scripts/mod/devicetable-offsets.s] Error 1
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: *** Waiting for unfinished jobs....





I am receiving the above error can anybody tell the solution for the same

  • 0

    After I source the settings32.sh file, I've always compiled the kernel with:

    make ARCH=arm UIMAGE_LOADADDR=0x8000 CROSS_COMPILE=arm-xilinx-linux-gnueabi- uImage

    Perhaps the GCC being called by the kernel build system (the one in your path) is incorrect?

    Also, it's a good idea (at least the first time in a new kernel tree) to start with a "make mrproper" to make sure you don't have anything weird hanging around from a previous build. It looks like the build tool is