Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled
On Thu, 20 Oct 2016 18:13:05 -0500 "S. R. Wright" <srw6666@gmail.com> wrote:
> I agree. When the version changes from 6.2.0-6 to 6.2.0-7, only bug
> fixes should be included, not changes in functionality. In this case
> setting enable-default-pie essentially broke backwards compatibility.
> Kernel code that built in -6 failed to build in -7. That, I agree,
> should be considered a bug, and the change should be rolled back.
>
> -- sRw
I support this statement about changing functionality of such an important tool.
At least a recipe how to get the old behavior should be documented.
>
> On 10/20/2016 05:49 PM, Ben Hutchings wrote:
> > On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote:
> >> It's not a GCC bug but kind of new feature.
> > It's a bug when a compiler fails to compile valid code.
> >
> > Ben.
> >
> >> Take a look at this changelog entry:
> >> gcc-6 (6.2.0-7) unstable; urgency=medium
> >>
> >> [ Matthias Klose ]
> >> * Configure with --enable-default-pie and pass -z now when pie is enabled;
> >> on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.
> >> Closes: #835148.
> >>
> >> Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in
> >> beginning of CFLAGS to build kernel successfully.
> >>
But does this generate the same output as without -enable-default-pie?
Some parts of the kernel do use -fpic or -fPIC. Which directive prevails?
> >> I'm currently looking for correct way to do this trick.
Regards,
jvp.
Reply to: