Re: Enabling -fstack-clash-protection for trixie [armhf rebuild]
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.
>
> Thank you so much, this is great! There's not much fallout.
>
> 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 bit code natively, so at
> least from the point of view of the underlying hardware this shouldn't
> be a problem.
>
> I've tried the following on a m6g.medium and it did the right thing:
>
> sbuild-createchroot --arch=armhf --components=main,contrib,non-free,non-free-firmware sid /srv/sid-armhf
Hi,
Sorry for the delay in answering your email.
Is this still of interest? Yes, that would be possible.
Lucas
Reply to: