On Sun, 2020-02-16 at 16:27 +0000, Ben Hutchings wrote: > This was discussed on IRC with Julien Cristau, but unfortunately I > didn't save a log. The main points that came up were: > > * Executables built for the O32 FP64 ABI require this kernel config > change and older kernel versions will refuse to load them. So the > kernel needs to be upgraded before installing any binaries built > for the new FP ABI. > > * Normally the support for an additional ABI would be included in > release N.0 and used in N+1. Since this was not present in 10.0, > it > would be possible for users to start upgrading to bullseye while > still running a kernel that does not support O32 FP64. We need to > prevent them getting a broken system. > > * Julien proposed that libc6 would have a preinst check on the kernel > when it is changed to use the new FP ABI. Presumably all binaries > built for the new FP ABI should also have a versioned dependency on > at least this version of libc6. > > So I don't see any reason not to update the kernel configuration > already, as it will remain compatible with the O32 FPXX binaries in > buster. Only the user-space changes in unstable (libc6 and > toolchain) need to be carefully coordinated.
As far as I can see, this was enabled in 4.19.118-1, but is about to be reverted due to causing issues. Is that accurate? If so, should we close this request now? Regards, Adam
