On 2023-10-27 14:29 +0100, Steve McIntyre wrote:
>
> Are either of those ports (armeb/arm64ilp32) actually useful / alive
> at this point?
No, but if someone did try to build a package for those it would be
incorrect for dpkg to enable these flags. The chances of anyone
actually doing that are pr
On Fri, Oct 27, 2023 at 02:29:30PM +0100, Steve McIntyre wrote:
> Are either of those ports (armeb/arm64ilp32) actually useful / alive
> at this point?
Not that I have seen. I didn't think anything other than the IXP ever
really used big endian and that's a long time ago. arm64ilp32 seems
to ser
On Fri, Oct 27, 2023 at 03:23:10PM +0200, Emanuele Rocca wrote:
>Hi Guillem,
>
>On 2023-10-27 04:33, Guillem Jover wrote:
>> Checking now again, I realize Wookey mentioned enabling this for the 3
>> arm arches (those would be arm64, armhf and armel), so the patch I
>> provided would match that. But
Hi Guillem,
On 2023-10-27 04:33, Guillem Jover wrote:
> Checking now again, I realize Wookey mentioned enabling this for the 3
> arm arches (those would be arm64, armhf and armel), so the patch I
> provided would match that. But I was wondering now what about armeb and
> arm64ilp32? I mean, I assu
Hi!
On Thu, 2023-10-26 at 12:55:32 +0200, Guillem Jover wrote:
> On Thu, 2023-10-26 at 11:40:53 +0200, Emanuele Rocca wrote:
> > Package: dpkg-dev
> > Version: 1.22.0
> > Severity: normal
> > -fstack-clash-protection is supposed to be enabled by default on amd64,
> > arm64, armhf, and armel since
5 matches
Mail list logo
