Bug#835148: please do not make GCC incompatible, we have dpkg-buildflags for this! (was Re: Bug#837420: Processed: PIE FTBFS are now RC)
2016-10-21 19:11 GMT+02:00 Thorsten Glaser <firstname.lastname@example.org>:
> Adrian Bunk dixit:
>>gcc-6 6.2.0-7 uploaded to unstable on Tue 18 Oct 2016 defaults to PIE,
>>see #835148 for details.
> Oh, thanks.
> This is *so* *totally* the wrong approach, especially as we
> have dpkg-buildflags, which was introduced *precisely* for
> this purpose, and to make Debian’s GCC not incompatible even
> more with the rest of the world.
You may have missed them, but there was several lengthy threads 
on debian-devel discussing the possible solutions including the
inapplicability of dpkg-buildflags for this problem.
However, if you do have a better _working_ solution for enabling PIE
archive-wide, please share that.
I'm exploring possible options like patching (upstream) GCC to disable
PIE for kernel or patching (upstream) kernel to disable PIE when it can
AFAIK the linux package is the only problematic package were the
maintainer refused to disable PIE from packaging scripts.