[yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Khem Raj]

On 17-03-08 19:01:05, Tom Rini wrote:
> On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote:
> > On 17-03-08 18:28:21, Tom Rini wrote:
> > > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote:
> > > 
> > > > openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot to
> > > > fail to compile:
> > > > 
> > > > 	arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program headers, try linking with -N
> > > > 
> > > > Building with -N does fix the issue, so this patch simply adds that flag to
> > > > the build so it succeeds.
> > > > 
> > > > This has been build-tested, as well as run-tested on the firefly.
> > > > 
> > > > Signed-off-by: Trevor Woerner <twoerner at gmail.com>
> > > 
> > > Unless there's an immediate need I would ask holding off on this for a
> > > bit, I want to track down why this is happening.
> > 
> > perhaps linker map files from 2.27 and 2.28 binutils will help to
> > understand it
> 
> Nothing is standing out yet:
> https://lists.denx.de/pipermail/u-boot/2017-March/283278.html
> https://lists.denx.de/pipermail/u-boot/2017-March/283286.html

I see that .data.rel.ro are generated eventhough they are empty they
appear to be in final link this section will hold constant variables
that gcc sees and needs dynamic relocation, that probably is not
relevant to u-boot since its linked stand-alone

Can you try to do just the final link with 2.28 and all built with 2.27
and see if it still happens, want to rule out assembler

> 
> I'm asking Trevor to poke at something that would change where we link
> things at and perhaps there's a linker bug here (this platform says that
> we link U-Boot at 0x0).
> 
> -- 
> Tom