From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ld-wrapper mislinks at91bootstrap
Date: Tue, 7 Nov 2017 09:37:07 +0100 [thread overview]
Message-ID: <20171107083707.o6g3kefqhyp5mqok@pengutronix.de> (raw)
In-Reply-To: <20171107072617.el5c7lnz7hryg3eh@lenoch>
On Tue, Nov 07, 2017 at 08:26:17AM +0100, Ladislav Michl wrote:
> On Tue, Nov 07, 2017 at 08:11:17AM +0100, Ladislav Michl wrote:
> > On Mon, Nov 06, 2017 at 07:58:58PM +0100, Ladislav Michl wrote:
> > > Hi there,
> > >
> > > I just added new platform (at91) to my BSP and configured at91bootstrap
> > > v3.8.9.
> > >
> > > Problem is that PTXDist-2017.10 produces way too large binary:
> > > 2099622 at91sam9260ek-dataflashboot-barebox-3.8.9.bin
> > > while correct size is:
> > > 2470 at91sam9260ek-dataflashboot-barebox-3.8.9.bin
> > >
> > > Problem turned out to be ld-wrapper script or something it calls.
> > > Just replacing ld-wrapper in ptxdist-2017.10.0/scripts/wrapper to point
> > > directly to arm-v5te-linux-gnueabi-ld is enough to solve problem.
> > > Does anyone clue where to look? Call path is:
> > > sysroot-host/lib/wrapper in $PATH where
> > > arm-v5te-linux-gnueabi-ld -> ptxdist-2017.10.0/scripts/wrapper/ld-wrapper
> >
> > So, ld-wrapper is adding:
> > --- at91sam9260ek-dataflashboot-barebox-3.8.9.map 2017-11-07 07:50:28.819011233 +0100
> > +++ at91sam9260ek-dataflashboot-barebox-3.8.9.map 2017-11-07 07:47:48.605530524 +0100
> > @@ -155,6 +155,11 @@
> >
> > 0x0000000000000000 . = ALIGN (0x4)
> >
> > +.note.gnu.build-id
> > + 0x0000000000000000 0x24
> > + .note.gnu.build-id
> > + 0x0000000000000000 0x24 linker stubs
> > +
> > .text 0x0000000000200000 0x1a0
> > 0x0000000000200000 _stext = .
> > *(.text)
> >
> > Modifying at91bootstrap's Makefile to do --remove-section=.note.gnu.build-id
> > fixes it.
> >
> > Are there other options to fix this?
>
> Well, I'll fix upstream the same way kernel handles this.
> Kernel is always right: https://lkml.org/lkml/2011/12/15/162
> Another option is to use u-boot way, ie. nicely align a embed
> this section into binary, but as every byte matters here, lets
> not do this.
You can also add TARGET_BUILD_ID to <PKG>_WRAPPER_BLACKLIST. We do the same
for the kernel.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-11-07 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 18:58 Ladislav Michl
2017-11-07 7:11 ` Ladislav Michl
2017-11-07 7:26 ` Ladislav Michl
2017-11-07 8:37 ` Michael Olbrich [this message]
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=20171107083707.o6g3kefqhyp5mqok@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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