linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: vdso: work-around broken ELF toolchains in Makefile
Date: Fri, 19 Jun 2015 09:47:46 -0500	[thread overview]
Message-ID: <55842B92.4090702@mentor.com> (raw)
In-Reply-To: <1434718593-3648-1-git-send-email-will.deacon@arm.com>

On 06/19/2015 07:56 AM, Will Deacon wrote:
> When building the kernel with a bare-metal (ELF) toolchain, the -shared
> option may not be passed down to collect2, resulting in silent corruption
> of the vDSO image (in particular, the DYNAMIC section is omitted).

I checked arch/arm with

arm-none-eabi-gcc (Fedora 4.9.2-3.fc21) 4.9.2

and it doesn't seem to be affected.  Do you know whether the toolchain
issue is aarch64-specific?

  parent reply	other threads:[~2015-06-19 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 12:56 [PATCH] arm64: vdso: work-around broken ELF toolchains in Makefile Will Deacon
2015-06-19 14:10 ` Catalin Marinas
2015-06-19 14:47 ` Nathan Lynch [this message]
2015-06-19 14:55   ` Will Deacon

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=55842B92.4090702@mentor.com \
    --to=nathan_lynch@mentor.com \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).