Re: Enabling -fstack-clash-protection for trixie [armhf rebuild]

2024-01-12 Thread Lucas Nussbaum
Hi, I finally got time to perform those archive rebuilds. Results are available at http://qa-logs.debian.net/2024/01/11/ I did a first archive rebuild (all packages on arm64, armhf, armel), and then did a second one, restricted to packages that failed at on at least one architecture. Results in

Re: Enabling -fstack-clash-protection for trixie [armhf rebuild]

2023-11-25 Thread Emanuele Rocca
Hello Lucas! On 2023-10-25 08:55, Lucas Nussbaum wrote: > On 14/08/23 at 14:53 +0200, Emanuele Rocca wrote: > > I'm not sure how the deal with AWS is (how many credits we have > > available and such) but would it be possible to repeat the experiment > > for armhf too? The Neoverse cpus can run 32

Re: Enabling -fstack-clash-protection for trixie [armhf rebuild]

2023-11-02 Thread Emanuele Rocca
Hi Lucas! On 2023-10-25 08:55, Lucas Nussbaum wrote: > Is this still of interest? Not really, we've flipped the switch now. Thanks nonetheless. :-) Emanuele

Re: Enabling -fstack-clash-protection for trixie [armhf rebuild]

2023-10-25 Thread Lucas Nussbaum
On 14/08/23 at 14:53 +0200, Emanuele Rocca wrote: > Hi Lucas, > > On 2023-08-12 08:18, Lucas Nussbaum wrote: > > Results: > > http://qa-logs.debian.net/2023/08/11.stackclash-arm/ > > > > I only included logs for builds that succeeded in a vanilla build, > > but failed with the custom build. > >