Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel-arch: Force BFD kernel when using gcc for linking
Date: Wed, 19 Aug 2015 14:59:08 -0500	[thread overview]
Message-ID: <55D4E00C.9060601@mentor.com> (raw)
In-Reply-To: <1440006296-15277-1-git-send-email-raj.khem@gmail.com>

On 08/19/2015 12:44 PM, Khem Raj wrote:
> We redefine LD to point to ld.bfd when building kernel, which works in
> most cases since kbuild system calls out for bare LD most of the time,
> however some of newer kernels e.g. 4.1+ have some code added which can
> call gcc directly to do the linking job e.g. arm vdso code
> 
> This causes build failures when we have configured the default cross
> toolchain to use gold linker as default. Errors like
> 
> BFD: arch/arm/vdso/vdso.so: Not enough room for program headers, try
> linking with -N
> | arm-angstrom-linux-gnueabi-objcopy:arch/arm/vdso/vdso.so[.hash]: Bad
> value
> 
> start happening.
> 
> With this patch we force gcc to choose bfd linker as well


This is fixed upstream as of:

commit d2b30cd4b7223a96e606dfc8120626f66d81e091
Author: Nathan Lynch <nathan_lynch@mentor.com>
Date:   Wed Jun 3 00:41:15 2015 +0100

    ARM: 8384/1: VDSO: force use of BFD linker

which should make it to 4.1-stable soon.



  reply	other threads:[~2015-08-19 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 17:44 [PATCH] kernel-arch: Force BFD kernel when using gcc for linking Khem Raj
2015-08-19 19:59 ` Nathan Lynch [this message]
2015-08-19 20:12   ` Burton, Ross
2015-08-19 20:15     ` Bruce Ashfield
2015-08-19 22:52     ` Khem Raj

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=55D4E00C.9060601@mentor.com \
    --to=nathan_lynch@mentor.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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