Re: Enabling -fstack-clash-protection for trixie [armhf rebuild]
- To: Lucas Nussbaum <lucas@debian.org>
- Cc: debian-devel@lists.debian.org, debian-arm@lists.debian.org
- Subject: Re: Enabling -fstack-clash-protection for trixie [armhf rebuild]
- From: Emanuele Rocca <ema@debian.org>
- Date: Sat, 25 Nov 2023 13:43:16 +0100
- Message-id: <[🔎] ZWHr5CXotGqdrMcF@ariel>
- In-reply-to: <ZTlktPJG7pq-UMVO@grub.nussbaum.fr>
- References: <ZNAPw3Im0B8Dn495@pisco.westfalen.local> <ZNSkkyFwOZoMvbNA@ariel> <ZNTbiQqnbxzvHsFx@grub.nussbaum.fr> <ZNT6yDOQWq3bQpeJ@ariel> <ZNckSvqObPUIlan3@grub.nussbaum.fr> <ZNojt1pZBD27/ErD@ariel> <ZTlktPJG7pq-UMVO@grub.nussbaum.fr>
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 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
[...]
> Sorry for the delay in answering your email.
> Is this still of interest? Yes, that would be possible.
If the offer is still valid, yes please. :-)
Emanuele
Reply to: