All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libmemcached: don't use -fPIE and -pie with FLAT binaries
Date: Tue, 12 May 2015 13:26:32 +0200	[thread overview]
Message-ID: <20150512132632.2cbbc566@free-electrons.com> (raw)
In-Reply-To: <87d226iwpp.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Tue, 12 May 2015 00:19:14 +0200, Peter Korsgaard wrote:

> BINFMT_FLAT implies BR2_STATIC_LIBS and (elf) static libraries should
> also not be built with -fPIE / -pie, right?
> 
> Is there any specific reason to only do this workaround for BINFMT_FLAT?

Actually, I'm a bit confused. Shouldn't FLAT binaries be PIE ? Since
there's no MMU, each binary will be loaded at a different address, so
binaries should be PIE, no?

But the original reason why I removed -pie is because of:

  https://www.mail-archive.com/toolchain-devel at blackfin.uclinux.org/msg02113.html

For the exact same error, Mike Frysinger says to remove the -pie flag.

Hum, http://www.kdvelectronics.eu/uClinux-cisco2500/exotica.html seems
to indicate that PIE is not required in all cases for FLAT binaries.

I would tend to trust Mike Frysinger on this, though :)

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

  reply	other threads:[~2015-05-12 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 20:55 [Buildroot] [PATCH] libmemcached: don't use -fPIE and -pie with FLAT binaries Thomas Petazzoni
2015-05-11 22:17 ` Romain Naour
2015-05-11 22:19 ` Peter Korsgaard
2015-05-12 11:26   ` Thomas Petazzoni [this message]
2015-05-12 12:20     ` Peter Korsgaard
2015-05-12 12:22       ` Thomas Petazzoni
2015-05-12 13:02         ` Peter Korsgaard
2015-05-12 14:17 ` Peter Korsgaard

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=20150512132632.2cbbc566@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.