summaryrefslogtreecommitdiff
path: root/drivers/qe
diff options
context:
space:
mode:
authorPeng Fan <Peng.Fan@freescale.com>2015-12-03 09:47:48 +0800
committerPeng Fan <Peng.Fan@freescale.com>2015-12-03 10:24:34 +0800
commit93dd4a9c59eb43862a95035a25759cf4f097b19c (patch)
tree45ed2e486194fabca87957788887b27755d8e765 /drivers/qe
parent6cdc3c37b96de9e9f42b79ccfeceda50518a9344 (diff)
downloadu-boot-imx-93dd4a9c59eb43862a95035a25759cf4f097b19c.zip
u-boot-imx-93dd4a9c59eb43862a95035a25759cf4f097b19c.tar.gz
u-boot-imx-93dd4a9c59eb43862a95035a25759cf4f097b19c.tar.bz2
MLK-11946 arm: config: disable pic when compiling code
Android's tool chain enable the -mandroid at default. This option will enable the -fpic, which cause uboot compilation failure: " LD u-boot u-boot contains unexpected relocations: R_ARM_ABS32 R_ARM_RELATIVE " In my testcase, arm-linux-androideabi-gcc-4.9 internally enables '-fpic', so when compiling code, there will be relocation entries using type R_ARM_GOT_BREL and .got section. When linking all the built-in.o using ld, there will be R_ARM_ABS32 relocation entry and .got section in the final u-boot elf image. This can not be handled by u-boot, since u-boot only expects R_ARM_RELATIVE relocation entry. arm-poky-linux-gnueabi-gcc-4.9 default does not enable '-fpic', so there is not .got section and R_ARM_GOT_BREL in built-in.o. And in the final u-boot elf image, all relocation entries are R_ARM_RELATIVE. we can pass '-fno-pic' to xxx-gcc to disable pic. whether the toolchain internally enables or disables pic, '-fno-pic' can work well. Signed-off-by: Peng Fan <Peng.Fan@freescale.com>
Diffstat (limited to 'drivers/qe')
0 files changed, 0 insertions, 0 deletions