public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2015.01-rc2 released
Date: Tue, 25 Nov 2014 07:30:10 -0500	[thread overview]
Message-ID: <20141125123010.GY21184@bill-the-cat> (raw)
In-Reply-To: <20141125111929.512d4b7d@amdc2363>

On Tue, Nov 25, 2014 at 11:19:29AM +0100, Lukasz Majewski wrote:
> Hi Guillaume,
> 
> > 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)
> > ********************************************************************************
> > 
> 
> I experience the same issue:

The patch is http://patchwork.ozlabs.org/patch/414042/ but I'd like a
few more people to review / test it.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141125/f1fdee53/attachment.pgp>

  parent reply	other threads:[~2014-11-25 12:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 22:13 [U-Boot] [ANN] U-Boot v2015.01-rc2 released Tom Rini
2014-11-25  8:51 ` Hans de Goede
2014-11-26 16:24   ` Tom Rini
2014-11-25  8:57 ` Wolfgang Denk
2014-11-25 10:06 ` Guillaume Gardet
2014-11-25 10:19   ` Lukasz Majewski
2014-11-25 11:17     ` Guillaume Gardet
2014-12-01  9:20       ` Pierre Aubert
2014-11-25 12:30     ` Tom Rini [this message]
2014-11-25 12:58       ` Guillaume Gardet
2014-11-25 14:37 ` Guillaume Gardet
  -- strict thread matches above, loose matches on Subject: below --
2015-02-17 20:25 Tom Rini
2015-02-17 20:40 ` Simon Glass
2015-02-18  5:34 ` Sinan Akman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141125123010.GY21184@bill-the-cat \
    --to=trini@ti.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox