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 13:19:12 -0500	[thread overview]
Message-ID: <20170308181912.GA22356@linux-uys3> (raw)
In-Reply-To: <20170308172047.GC19897@bill-the-cat>

On Wed 2017-03-08 @ 12:20:47 PM, Tom Rini wrote:
> On Wed, Mar 08, 2017 at 11:57:58AM -0500, Trevor Woerner wrote:
> > On Wed 2017-03-08 @ 10:35:19 AM, Tom Rini wrote:
> > > perhaps we can do -N --no-omgic (which negates most of what -N does
> > 
> > Unfortunately "-N --no-omagic" doesn't succeed either (same problem):
> > 
> > 	arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program headers, try linking with -N
> 
> OK.  Lets dig a little harder.  Do you have an older binutils around as
> well?  It would be good to compare the objdump between the older version
> and newer version with -N passed in as well.  Thanks!

No problem, OpenEmbedded FTW!! ;-)
(it's quite easy to switch between them and build, using OE)

Would comparing the map files suffice? If I build u-boot twice (once with
binutils-2.27 and once with binutils-2.28) and add the "-N" flag to the
linking for both builds, comparing the map files I get:

	$ diff -u 2.27-with-N/u-boot.map 2.28-with-N/u-boot.map 
	--- 2.27-with-N/u-boot.map      2017-03-08 13:05:32.380107036 -0500
	+++ 2.28-with-N/u-boot.map      2017-03-08 13:07:50.240330617 -0500
	@@ -7084,6 +7084,7 @@
	 
	 .data           0x0000000000043678     0x296c
	  *(.data*)
	+ .data.rel.ro   0x0000000000043678        0x0 arch/arm/cpu/armv7/start.o
	  .data.rk3288_otg_data
			 0x0000000000043678       0x2c arch/arm/mach-rockchip/built-in.o
	  .data.rk3288_dmc_ops
	@@ -7946,6 +7947,9 @@
	  *(.rel*)
	  .rel.got       0x0000000000047cc0        0x0 arch/arm/cpu/armv7/start.o
	  .rel.plt       0x0000000000047cc0        0x0 arch/arm/cpu/armv7/start.o
	+ .rel.bss       0x0000000000047cc0        0x0 arch/arm/cpu/armv7/start.o
	+ .rel.data.rel.ro
	+                0x0000000000047cc0        0x0 arch/arm/cpu/armv7/start.o
	  .rel.iplt      0x0000000000047cc0        0x0 arch/arm/cpu/armv7/start.o
	  .rel.text      0x0000000000047cc0       0x20 arch/arm/cpu/armv7/start.o
	  .rel.vectors   0x0000000000047ce0       0x38 arch/arm/cpu/armv7/start.o



If this isn't what you're looking for, please suggest what you'd like and I'll
give it a try.

Best regards,
	Trevor

  reply	other threads:[~2017-03-08 18:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  7:39 [U-Boot] linking rockchip-linux/u-boot.git with binutils-2.28 Trevor Woerner
2017-03-08  8:22 ` 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 [this message]
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=20170308181912.GA22356@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.