From mboxrd@z Thu Jan  1 00:00:00 1970
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
Date: Fri, 29 Jan 2016 17:42:45 +0100
Subject: [U-Boot] [RFC V1] arm: config: enforce -fno-pic for gcc
In-Reply-To: <1449302026-32675-1-git-send-email-Peng.Fan@freescale.com>
References: <1449302026-32675-1-git-send-email-Peng.Fan@freescale.com>
Message-ID: <20160129174245.3b1c9b1d@lilith>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hello Peng,

On Sat, 5 Dec 2015 15:53:46 +0800, Peng Fan <Peng.Fan@freescale.com>
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
> "

Any idea why Android's toolchain has -fpic enabled?

> we can pass '-fno-pic' to xxx-gcc to disable pic. whether
> the toolchain internally enables or disables pic, '-fno-pic'
> can work well.

No problem apparently with this RFC. If you submit a non-RFC patch
I will apply it.

Amicalement,
-- 
Albert.