From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Sat, 30 Jan 2016 09:59:52 -0500 Subject: [U-Boot] [PATCH V2] arm: config: enforce -fno-pic for gcc In-Reply-To: <1454127049-4851-1-git-send-email-peng.fan@nxp.com> References: <1454127049-4851-1-git-send-email-peng.fan@nxp.com> Message-ID: <20160130145952.GJ27374@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sat, Jan 30, 2016 at 12:10:49PM +0800, Peng Fan wrote: > 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 > Cc: Albert Aribaud Reviewed-by: Tom Rini -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: