All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] linking rockchip-linux/u-boot.git with binutils-2.28
Date: Wed, 8 Mar 2017 02:39:00 -0500	[thread overview]
Message-ID: <20170308073900.GA14364@linux-uys3> (raw)

Hi,

It appears as though linking u-boot with binutils-2.28 fails:

	arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program headers, try linking with -N

openembedded-core master just upgraded from binutils-2.27 to 2.28, everything
builds fine with 2.27 but fails (see above) with 2.28.

What's odd is that googling around makes it sound like the problem is with the
linker script. But the code isn't changing, only the linker. So the old linker
found enough room, but the new linker things it's running out?

Has anyone else noticed this?

Does anyone have thoughts on solving this?

Thanks and best regards,
	Trevor

             reply	other threads:[~2017-03-08  7:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  7:39 Trevor Woerner [this message]
2017-03-08  8:22 ` [U-Boot] linking rockchip-linux/u-boot.git with binutils-2.28 Trevor Woerner
2017-03-08  8:43   ` Peter Robinson
2017-03-08 15:18     ` Simon Glass
2017-03-08 15:35       ` Tom Rini
2017-03-08 16:57         ` Trevor Woerner
2017-03-08 17:20           ` Tom Rini
2017-03-08 18:19             ` Trevor Woerner
2017-03-08 18:41               ` Tom Rini
2017-03-08 19:53                 ` Trevor Woerner
2017-03-08 21:33                   ` Tom Rini
2017-03-08 22:32                     ` Trevor Woerner
2017-03-08 22:33                       ` Trevor Woerner
2017-03-08 23:17                       ` Tom Rini
2017-03-09  4:36                         ` Trevor Woerner
2017-03-09 12:19                           ` Tom Rini
2017-03-08 16:43     ` Trevor Woerner
2017-03-08 16:51       ` Peter Robinson

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=20170308073900.GA14364@linux-uys3 \
    --to=twoerner@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.