From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Gardet Date: Tue, 25 Nov 2014 11:06:24 +0100 Subject: [U-Boot] [ANN] U-Boot v2015.01-rc2 released In-Reply-To: <20141124221339.GW21184@bill-the-cat> References: <20141124221339.GW21184@bill-the-cat> Message-ID: <547454A0.1030106@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le 24/11/2014 23:13, Tom Rini a ?crit : > Hey all, > > I've pushed v2015.01-rc2 out to the repository and tarballs should exist > soon. > > I'm tagging later in the day than I wanted to, but that's OK. > > There's a fair number of things that've gone in since -rc1, but I think > that's OK. And there's a few things that still need to go in. > > For example, I just pushed the changes to allow bigger files to be read > but that's broken MIPS+private libgcc and ARM+hf toolchain and others > too. I posted a patch for this and tested it locally with a 32MB file > but I'd like others to review too (Thanks Simon!) before pushing it in. > > As always, if anything else is broken please speak up. I guess this the ARM+hf problem you mentioned: ******************************************************************************** LD u-boot ld.bfd: error: /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(bpabi.o) uses VFP register arguments, u-boot does not ld.bfd: failed to merge target specific data of file /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(bpabi.o) ld.bfd: error: /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(_divdi3.o) uses VFP register arguments, u-boot does not ld.bfd: failed to merge target specific data of file /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(_divdi3.o) ld.bfd: error: /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(_udivdi3.o) uses VFP register arguments, u-boot does not ld.bfd: failed to merge target specific data of file /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/libgcc.a(_udivdi3.o) ******************************************************************************** Is there any pending patch to fix this one? Guillaume