mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Freyther <holger@moiji-mobile.com>
To: barebox@lists.infradead.org
Subject: Re: Linking issue with ld.bfd 2.28.0.20170307
Date: Mon, 17 Apr 2017 07:35:19 +0200	[thread overview]
Message-ID: <2CBFB5C4-AB2B-448E-9127-DEBE0B12E168@moiji-mobile.com> (raw)
In-Reply-To: <CCE0355C-0078-435E-A307-9D64235CC014@moiji-mobile.com>


> On 30. Mar 2017, at 20:49, Holger Freyther <holger@moiji-mobile.com> wrote:
> 
> Hi,

Hi!

> I am rebuilding the bootloader with gcc6 and the above version
> of binutils and it is failing to link with .bfd but is working
> with .gold.
> 
> Is this known? Is anyone else seeing this issue? And no I did
> not try linking with -N and I have no idea what ld thinks is
> the program headers here.

my steps to reproduce this with Yocto's gcc-6.3 and ld.bfd
2.28.0.20170307 are the following. CROSS_COMPILE points into
the sysroot of a build on poky master.

git clone --branch=hfreyther/v2017.03-rebase git://git.sysmocom.de/barebox
cd barebox/
wget -O .config "http://git.sysmocom.de/poky/meta-sysmocom-bsp/plain/recipes-bsp/barebox/barebox-sysmobts/defconfig?id=39afcd35ae40b8468868f1e942706dec11e03961"
make ARCH=arm


.../arm-poky-linux-gnueabi-ld: .tmp_barebox1: Not enough room for program headers, try linking with -N
.../arm-poky-linux-gnueabi-ld: final link failed: Bad value
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-04-17  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 18:49 Holger Freyther
2017-04-17  5:35 ` Holger Freyther [this message]
2017-04-19 10:31   ` Sascha Hauer
2017-04-19 19:30     ` Панов Андрей
2017-04-21  9:54       ` Holger Freyther

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=2CBFB5C4-AB2B-448E-9127-DEBE0B12E168@moiji-mobile.com \
    --to=holger@moiji-mobile.com \
    --cc=barebox@lists.infradead.org \
    /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