From mboxrd@z Thu Jan 1 00:00:00 1970 From: Allen Martin Date: Fri, 18 May 2012 15:13:04 -0700 Subject: [U-Boot] [PATCH 9/9] tegra2: Remove USE_PRIVATE_LIBGCC and armv4t build flags In-Reply-To: <4FB1E57E.4090308@wwwdotorg.org> References: <1336633347-8049-1-git-send-email-amartin@nvidia.com> <1336633347-8049-10-git-send-email-amartin@nvidia.com> <4FB1E57E.4090308@wwwdotorg.org> Message-ID: <20120518221304.GA30009@nvidia.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, May 14, 2012 at 10:11:26PM -0700, Stephen Warren wrote: > On 05/10/2012 01:02 AM, Allen Martin wrote: > > -USE_PRIVATE_LIBGCC = yes > > However, we force this because the toolchains we typically use for > U-Boot are targeted at the A9 CPUs, and hence the libgcc there contains > ARMv7 instructions. Did I miss something in this series or earlier that > uses a different toolchain for the SPL, which includes an ARMv4 build of > libgcc? You're right, that's a mistake, I'll revert that line. There is a problem right now where if you have both SPL and USE_PRIVATE_LIBGCC turned on, the SPL build of libgcc tries to link against the main u-boot libgcc, which in itself is probably fine, except on a clean build it hasn't been built yet. So I'll have to fix that. -Allen -- nvpublic