> On Oct 26, 2021, at 11:07 AM, Robert Elz <k...@munnari.oz.au> wrote:
>
> Date: Tue, 26 Oct 2021 18:27:20 +0300
> From: Valery Ushakov <u...@stderr.spb.ru>
> Message-ID: <yxgewgwdqrbmm...@pony.stderr.spb.ru>
>
> | OTOH the old
> | *binaries* (using old dynamic libc, or linked with old static libc)
> | still need the kernel support.
>
> I think the point is that the "old dynamic libc" is the current libc,
> unless an old binary is so old that it linked against libc.11 or earlier
> (which means way back into the last millenium sometime).
>
> So not only is kernel support needed, libc (12) support is as well. Once
> the fabled libc version bump happens this will all change.
I mean, I could certainly fix it (and rev the symbol), just don’t know if it’s
worth the bother since it’s been broken for so long.
-- thorpej
