Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] quagga: disable PIE on ARC
Date: Fri, 10 Jul 2015 15:08:31 +0200	[thread overview]
Message-ID: <20150710150831.3ff095c8@free-electrons.com> (raw)
In-Reply-To: <559FB8AE.7020302@mind.be>

Dear Arnout Vandecappelle,

On Fri, 10 Jul 2015 14:21:02 +0200, Arnout Vandecappelle wrote:

>  What I mean is that we patch gcc and only support the pie option if that magic
> environment variable is set.
> 
>  But looking at the source, that's not going to be easy since the whole command
> line parsing is abstracted in a way that makes it difficult to hack something
> like that.
> 
>  Perhaps another solution is that we disable -pie in the spec file, and pass an
> alternative spec file which does have pie support in U-Boot:
> 
> UBOOT_MAKE_OPTS += \
> 	CC="$(TARGET_CC) -specs=path-to-specfile-with-pie"

In the end, this seems quite complicated. Not that many packages try to
build their executables as PIE, so maybe handling that on a per-package
basis is easier / less hacky.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-07-10 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 10:00 [Buildroot] [PATCH] quagga: disable PIE on ARC Alexey Brodkin
2015-07-09 20:14 ` Thomas Petazzoni
2015-07-09 21:30 ` Arnout Vandecappelle
2015-07-10  6:44   ` Thomas Petazzoni
2015-07-10  8:12     ` Alexey Brodkin
2015-07-10 10:08       ` Arnout Vandecappelle
2015-07-10 11:28         ` Alexey Brodkin
2015-07-10 12:21           ` Arnout Vandecappelle
2015-07-10 13:08             ` Thomas Petazzoni [this message]
2015-07-10 22:05               ` Arnout Vandecappelle

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=20150710150831.3ff095c8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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