From: Theodore Ts'o <tytso@mit.edu>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Michal Marek <mmarek@suse.com>,
linux-kbuild@vger.kernel.org, x86@kernel.org,
Al Viro <viro@ZenIV.linux.org.uk>,
Ben Hutchings <ben@decadent.org.uk>,
Sven Joachim <svenjoac@gmx.de>,
"Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: -fno-PIE, take #3
Date: Mon, 7 Nov 2016 01:30:15 -0500 [thread overview]
Message-ID: <20161107063015.s7j6wpimj5himjp2@thunk.org> (raw)
In-Reply-To: <20161104183940.30692-1-bigeasy@linutronix.de>
On Fri, Nov 04, 2016 at 07:39:37PM +0100, Sebastian Andrzej Siewior wrote:
> Debian gcc's is nowdays compiled with --enable-default-pie which means it does
> -fPIE by default. This breaks atleast x86-64 compiles.
> This is the third attempt to fix it, this time by using runtime detection of
> the -fno-PIE compiler switch (it was introduced in gcc 3.4, min required gcc is
> currently 3.2) so it can be backported to the stable kernels.
> As noted by Al this won't fix `git bisect' of stable kernels prio this commit.
> However using always a wrapper around gcc which adds -fno-PIE is not sollution
> I want to rely in future.
A wrapper around gcc which adds -fno-PIE doesn't work for the HOSTCC
builds, anyway:
% gcc -fno-PIE -o /tmp/hello /tmp/hello.c
/usr/bin/ld: /tmp/cckzDf9X.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
Alas, the only workaround I've found which doesn't involve bisecting
the kernel is to add "CC=gcc-5" to the Makefile invocation (assuming
gcc-5 is installed of course).
- Ted
next prev parent reply other threads:[~2016-11-07 6:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 18:39 -fno-PIE, take #3 Sebastian Andrzej Siewior
2016-11-04 18:39 ` [PATCH 1/3] kbuild: add -fno-PIE Sebastian Andrzej Siewior
2016-11-08 22:14 ` Michal Marek
2016-11-09 6:10 ` Ingo Molnar
2016-11-09 21:29 ` Michal Marek
2016-11-10 9:25 ` Ingo Molnar
2016-11-04 18:39 ` [PATCH 2/3] scripts/has-stack-protector: " Sebastian Andrzej Siewior
2016-11-04 18:39 ` [PATCH 3/3] x86/kexec: " Sebastian Andrzej Siewior
2016-11-07 6:30 ` Theodore Ts'o [this message]
2016-11-07 22:31 ` -fno-PIE, take #3 H. Peter Anvin
2016-11-08 13:42 ` Borislav Petkov
2016-11-08 22:51 ` Ben Hutchings
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=20161107063015.s7j6wpimj5himjp2@thunk.org \
--to=tytso@mit.edu \
--cc=ahferroin7@gmail.com \
--cc=ben@decadent.org.uk \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=svenjoac@gmx.de \
--cc=viro@ZenIV.linux.org.uk \
--cc=x86@kernel.org \
/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.