Hi!
On Sun, 2023-08-06 at 23:25:23 +0200, Moritz Mühlenhoff wrote:
> Following the procedure to modify default dpkg-buildflags I propose to
> enable -fstack-clash-protection on amd64. The bug for dpkg tracking this
> is #918914.
>
> | -fstack-clash-protection
> | Generate code to prevent stack cl
Hi!
On Thu, 2023-06-22 at 21:59:45 +0200, John Paul Adrian Glaubitz wrote:
> Apologies for the late reply!
No problem at all!
> On Thu, 2023-03-23 at 23:15 +0100, Guillem Jover wrote:
> > [ Sorry had not seen the reply until now when I was doing a pass
> > over submitted bug
Hi!
I'd like to get some feedback from porters and package maintainers,
given that this affects at least both groups. Some background first.
One of the reasons PIE has in the past not been enabled by default in
dpkg-buildflags, is because it introduced some slowness on some arches,
although this
Hi!
On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote:
> clone 845193 -1
> reassign -1 dpkg
> retitle -1 dpkg: please do not add -specs= flags only on some architectures
> thanks
I'm afraid I'll have to wontfix this because it is not really
implementable. See belo
Hi!
On Sun, 2016-08-21 at 08:22:09 +0200, Niels Thykier wrote:
> Kurt Roeckx:
> > On Wed, Aug 17, 2016 at 10:05:06PM +0200, ni...@thykier.net wrote:
> >> * If we were to enable -fPIE/-pie by default in GCC-6, should that change
> >>also apply to this port? [0]
> >
> > If -fPIE is the default
5 matches
Mail list logo