[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161025073002.czwx2hysib77i7d5@linutronix.de>
Date: Tue, 25 Oct 2016 09:30:02 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Sven Joachim <svenjoac@....de>
Cc: Joe Perches <joe@...ches.com>, Adam Borowski <kilobyte@...band.pl>,
Michal Marek <mmarek@...e.com>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, ben@...adent.org.uk
Subject: Re: [RFC PATCH] kbuild: add -fno-PIE
On 2016-10-24 19:32:30 [+0200], Sven Joachim wrote:
> On 2016-10-24 09:43 +0200, Sebastian Andrzej Siewior wrote:
>
> > On 2016-10-24 09:38:49 [+0200], Sven Joachim wrote:
> >>
> >> But make still fails with it. :-(
> >
> > try setting CONFIG_CC_STACKPROTECTOR_NONE=y and please let me know if
> > the resulting kernel built with v3.2 gcc boots & works.
>
> Sorry, I don't have gcc 3.2 around, and my gcc 3.3 environment produces
> assembler errors in arch/x86/entry/entry_32.S. Maybe binutils 2.15 is
> not recent enough anymore?
so we use stone age gcc but take latest binutils and kernel? What about
lifting the limit of gcc 3.2? Is there any use case in 2016 to use gcc
3.2 on a recent kernel except whether it still compiles or not?
Sebastian
Powered by blists - more mailing lists