Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] trousers: disable pie option on ARC
Date: Fri, 15 Jan 2016 13:56:07 +0000	[thread overview]
Message-ID: <1452866166.18381.50.camel@synopsys.com> (raw)
In-Reply-To: <20160115143357.422dab52@free-electrons.com>

Hi Thomas, Lada,

On Fri, 2016-01-15 at 14:33 +0100, Thomas Petazzoni wrote:
> Dear Lada Trimasova,
> 
> On Fri, 15 Jan 2016 15:21:48 +0300, Lada Trimasova wrote:
> > ARC gcc understands "-pie" option and attempts to generate PIE
> > binaries as of today PIE is not really supported for user-space
> > applications. So we provide option which can make relro and pie usage
> > optional and disable PIE detection if building for ARC. Also AUTORECONF
> > option should be added because of modified configure.in and Makefile.am
> > files.
> > 
> > Signed-off-by: Lada Trimasova <ltrimas@synopsys.com>
> > Cc: Alexey Brodkin <abrodkin@synopsys.com>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > Cc: Peter Korsgaard <peter@korsgaard.com>

[snip]

> Now that I think of it, what would be even better than adding a new
> config option is to simply test if the compiler is capable of linking a
> simple PIE binary. If the compiler is PIE capable, then trousers would
> use PIE, otherwise not.

I'm afraid that won't work for ARC. That's because simple apps could be
built but as we've seen already more complicated apps will fail to build.
I.e. we need to have an ability to force disable PIE on ARC.

Still check for PIE makes perfect sense but in addition to it we'll
need a way to disable that check and force disable PIE.

-Alexey

  reply	other threads:[~2016-01-15 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 12:21 [Buildroot] [PATCH] trousers: disable pie option on ARC Lada Trimasova
2016-01-15 13:33 ` Thomas Petazzoni
2016-01-15 13:56   ` Alexey Brodkin [this message]
2016-01-15 14:05     ` Thomas Petazzoni

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=1452866166.18381.50.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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