From: Joe Perches <joe@perches.com>
To: Sven Joachim <svenjoac@gmx.de>, Adam Borowski <kilobyte@angband.pl>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Marek <mmarek@suse.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
ben@decadent.org.uk
Subject: Re: [RFC PATCH] kbuild: add -fno-PIE
Date: Sun, 23 Oct 2016 12:23:18 -0700 [thread overview]
Message-ID: <1477250598.3561.4.camel@perches.com> (raw)
In-Reply-To: <87eg37niky.fsf@turtle.gmx.de>
On Sun, 2016-10-23 at 18:19 +0200, Sven Joachim wrote:
> On 2016-10-21 23:21 +0200, Adam Borowski wrote:
> > On Fri, Oct 21, 2016 at 01:16:00PM +0200, Sebastian Andrzej Siewior wrote:
> > > Debian started to build the gcc with --enable-default-pie by default
[]
> > > diff --git a/Makefile b/Makefile
[]
> > > @@ -398,7 +398,7 @@ KBUILD_CPPFLAGS := -D__KERNEL__
> > > KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
> > > -fno-strict-aliasing -fno-common \
> > > -Werror-implicit-function-declaration \
> > > - -Wno-format-security \
> > > + -Wno-format-security -fno-PIE \
> > > -std=gnu89
I've used this here instead:
KBUILD_CFLAGS += $(call cc-option,-fno-pie)
next prev parent reply other threads:[~2016-10-23 19:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:16 [RFC PATCH] kbuild: add -fno-PIE Sebastian Andrzej Siewior
2016-10-21 21:21 ` Adam Borowski
2016-10-23 16:19 ` Sven Joachim
2016-10-23 19:23 ` Joe Perches [this message]
2016-10-24 7:38 ` Sven Joachim
2016-10-24 7:43 ` Sebastian Andrzej Siewior
2016-10-24 17:32 ` Sven Joachim
2016-10-24 17:48 ` Joe Perches
2016-10-25 7:30 ` Sebastian Andrzej Siewior
2016-10-26 17:51 ` Sven Joachim
2016-10-27 7:28 ` Sebastian Andrzej Siewior
2016-10-28 23:00 ` Andrew Morton
2016-10-29 10:10 ` Tomas Janousek
2016-10-29 17:03 ` Sven Joachim
2016-10-29 19:21 ` Tomas Janousek
2016-10-29 21:18 ` Sven Joachim
2016-10-24 9:57 ` Joe Perches
2016-10-27 17:09 ` Shuah Khan
2016-10-28 8:09 ` Sebastian Andrzej Siewior
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=1477250598.3561.4.camel@perches.com \
--to=joe@perches.com \
--cc=ben@decadent.org.uk \
--cc=bigeasy@linutronix.de \
--cc=kilobyte@angband.pl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=svenjoac@gmx.de \
/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