CI: update the glibc version we use for aarch64

[DilumAluthge]

No description provided.

[DilumAluthge]

Hat-tip @staticfloat for providing this fix.

[DilumAluthge]

Okay, so the original issue (the glibc problem) seems to be fixed. But now there's a new test failure.

@Keno Is this test failure expected?

[Keno]

The glibc that comes with the rootfs likely wasn't built with -moutline-atomics (or more likely with a GCC version that doesn't have the initializer priority fix) which is required for rr to work. I think the way to fix this will be to bump the glibc version in Yggdrasil and then bumping the version here. Yggdrasil builds these things with rr compatibility.

[rocallahan]

So the patched glibc didn't work with the version of lldb or its dependencies that you tried to install? Can we just install a different version of lldb and not upgrade glibc?

[Keno]

We periodically bump the base debian version that we use to build the CI root images, but we didn't bump the rr ci config when that happened last, so it was still on old debian. So the new debian has a newer glibc than the patched one that we had prepared for rr. We could build an old debian with lldb, but I think building newer glibc is probably easier, since that's all automated. Otherwise the rr ci would need a special snowflake rootfs build for the older debian.

[Keno]

@DilumAluthge do you know what needs to be done for the glibc bump or do you need me to take care of it?

[rocallahan]

Looks like this PR is still failing.

I know you guys are busy but I hope we can get this fixed

[staticfloat]

It appears that when we unpack the new DebianGlibc version over the top of the rootfs it replaces /usr/include/string.h (along with all the other includes) but the compiler is complaining about that:

/usr/include/string.h:467:5: error: expected , or ; before __fortified_attr_access
 467  |     __fortified_attr_access (__write_only__, 1, 2);
      |     ^~~~~~~~~~~~~~~~~~~~~~~