From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2014-04-20
Date: Mon, 21 Apr 2014 13:58:07 +0200 [thread overview]
Message-ID: <20140421135807.3002c46f@skate> (raw)
In-Reply-To: <39A54937CC95F24AA2F794E2D2B66B1356CB9EA2@de02wembxa.internal.synopsys.com>
Dear Anton Kolesov,
On Mon, 21 Apr 2014 10:18:53 +0000, Anton Kolesov wrote:
> [AK:] This is a limitation of ARC uClibc port: our crt1.o doesn't support PIE (though it seems simple hello world can be compiled). Our uClibc developer (added to CC) is going to fix this in near future, but he has a lot of other tasks to do right now, so this might not happen immediately.
Why do we need a PIE executable here? As far as I understand, PIC is
mandatory for shared libraries, but PIE for executables is only needed
for security reasons, if you want to randomize the location of
executables in memory, at least in MMU-capable platforms.
So maybe we should just cook a patch to remove -fPIE when building
openswan ? I don't think we build any other package with -fPIE, so why
should openswan be different ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-21 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-20 Thomas Petazzoni
2014-04-21 9:49 ` [Buildroot] Analysis of build " Thomas Petazzoni
2014-04-21 10:18 ` Anton Kolesov
2014-04-21 11:58 ` Thomas Petazzoni [this message]
2014-04-21 13:29 ` Anton Kolesov
2014-04-21 20:12 ` Thomas Petazzoni
2014-04-21 13:47 ` Alexey Brodkin
2014-04-21 20:13 ` Thomas Petazzoni
2014-04-21 14:24 ` Yann E. MORIN
2014-04-21 17:03 ` Eric Le Bihan
2014-04-21 17:17 ` Yann E. MORIN
2014-04-21 17:56 ` Eric Le Bihan
2014-04-21 18:03 ` Yann E. MORIN
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=20140421135807.3002c46f@skate \
--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