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] Analysis of build results for 2014-04-20
Date: Mon, 21 Apr 2014 22:13:00 +0200	[thread overview]
Message-ID: <20140421221300.7229097f@skate> (raw)
In-Reply-To: <1398088076.25515.10.camel@abrodkin-8560l.internal.synopsys.com>

Dear Alexey Brodkin,

On Mon, 21 Apr 2014 13:47:57 +0000, Alexey Brodkin wrote:

> As Anton has just answered -fPIE/-pie is enabled in top-level
> Makefile.inc. But as I may see at least in master branch here
> https://github.com/xelerance/Openswan/blob/master/Makefile.inc it's
> very easy to override these settings with simple definitoin of
> USERCOMPILE and USERLINK variables.
> 
> So definitely it is doable. But another good question would be if this
> was done on purpose (which I cannot undersnad clearly from commit
> message because too many items were dropped in at once here -
> https://github.com/xelerance/Openswan/commit/6181d2b2999e112d47884dda48d1ca2916e2403e#diff-084b77e3e200296f6230945d5f0ea0ec)
> or not.
> 
> Another comment on PIE usage.
> I know for sure that many architectures (and more to come) use PIE for
> U-Boot (and here it is used on purpose for entire relocation of both
> code and data), so definitely PIE is required feature of toolchains
> and IMHO we don't want to escape it if it is used by packages
> developers.

Ok. However in the mean time, I think we could disable it for openswan,
no?

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

  reply	other threads:[~2014-04-21 20:13 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
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 [this message]
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=20140421221300.7229097f@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