From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Makefile: Fix linking with modern binutils
Date: Tue, 21 Mar 2017 19:13:44 -0400 [thread overview]
Message-ID: <20170321231344.GF19897@bill-the-cat> (raw)
In-Reply-To: <20170322090058.184b6dbb@roar.ozlabs.ibm.com>
On Wed, Mar 22, 2017 at 09:00:58AM +1000, Nicholas Piggin wrote:
> On Tue, 21 Mar 2017 11:16:50 -0400
> Tom Rini <trini@konsulko.com> wrote:
>
> > On Tue, Mar 21, 2017 at 08:59:04AM -0500, Jon wrote:
> >
> > > Likewise tested on Fedora rawhide with: binutils-2.28-5.fc27
> > >
> > > This patch allows our distro u-boot builds to succeed. +1
> > >
> > > Tested-by: Jon Disnard <jdisnard@gmail.com>
> >
> > Has anyone figure out what exactly is going on yet? It's pretty odd to
> > me that linking at 0x0 (or not) is what's causing new binutils to throw
> > this particular error out there. Thanks!
>
> Some discussion from binutils developers is here:
>
> https://patchwork.ozlabs.org/patch/699815/
That in turn seems to point to
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=ff45000fcb56b5b0f1a14a865d3541
as an example of how to correct the problem (what U-Boot is doing), and
we should make a patch similar to that it seems. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170321/d9352647/attachment.sig>
next prev parent reply other threads:[~2017-03-21 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 4:53 [U-Boot] [PATCH v2] Makefile: Fix linking with modern binutils Joel Stanley
2016-12-26 18:07 ` Tom Rini
2017-01-12 9:19 ` Sjoerd Simons
2017-03-21 13:59 ` Jon
2017-03-21 15:16 ` Tom Rini
2017-03-21 23:00 ` Nicholas Piggin
2017-03-21 23:13 ` Tom Rini [this message]
2017-03-22 12:53 ` Alan Modra
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=20170321231344.GF19897@bill-the-cat \
--to=trini@konsulko.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