Am 25.06.20 um 17:49 schrieb Thorsten Glaser:
> Michael Biebl dixit:
>
>> Is this workaround permanent or will systemd FTBFS again in the future?
>
> I’ve just verified that the upstream-merged fix, appearing in
> linux-libc-dev 5.7.6-1 in sid, fixes this permanently.
>
Great, thanks Thorsten.
Michael Biebl dixit:
>Is this workaround permanent or will systemd FTBFS again in the future?
I’ve just verified that the upstream-merged fix, appearing in
linux-libc-dev 5.7.6-1 in sid, fixes this permanently.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn •
On Wed, 8 Apr 2020, Michael Biebl wrote:
>> Is this workaround permanent or will systemd FTBFS again in the future?
It is not inherently permanent. If a new libseccomp version gets
uploaded it will pop back up. In these cases, I’ll most likely
notice it due to Multi-Arch skew (my x32 system has
Am 08.04.20 um 09:56 schrieb Michael Biebl:
> If seccomp support on x32 is causing so much trouble, we can just as
> well disable it in systemd for the time being by dropping libseccomp-dev
> from Build-Depends
... on x32 only, of course.
signature.asc
Description: OpenPGP digital signature
Am 07.04.20 um 14:26 schrieb Thorsten Glaser:
> retitle 954294 linux: __X32_SYSCALL_BIT being defined as UL constant breaks
> userspace
> reassign 954294
> found 954294 5.5.13-2
> thanks
>
> Dixi quod…
>
>>> -#define SCMP_SYS(x) (__SNR_##x)
>>> +#define SCMP_SYS(x)
5 matches
Mail list logo