scripts(toolchain): Update to NDK r28b

[fornwall]

It's time to start looking at updating to NDK r28!

• Changelog r28

Haven't tested much, but a lot of basic packages build.

Fixes #21628

[fornwall]

Have published a prebuilt builder image at https://hub.docker.com/repository/docker/fredrikfornwall/package-builder-r28b-v1, which can be used to save time as:

CONTAINER_NAME=ndk28-builder TERMUX_BUILDER_IMAGE_NAME=fredrikfornwall/package-builder-r28b-v1 ./scripts/run-docker.sh

[finagolfin]

We've only been updating to the LTS NDKs in recent years.

[fornwall]

We've only been updating to the LTS NDKs in recent years.

Ah right, r25, r26 and r27 were three consecutive LTS releases.

I wonder if it makes sense to continuously update to NDK stable releases without awaiting LTS ones, to more continuously adapt to toolchain changes as soon as they are out?

[finagolfin]

Honestly, their release process is a mess at this point, is "stable" still considered a rolling release? Who knows.

I definitely think it makes sense to adapt to the stable releases in a branch, but whether we should switch the whole repo over now is an open question. Maybe Henrik, @truboxl, @licy183, and other contributors have input...

[thunder-coding]

I'd suggest that we wait for r28c. Regardless of r28c being LTS or not, I guess we should go ahead with it

[licy183]

I'm afraid NDK r28* will not be the LTS release... See https://github.com/android/ndk/wiki

[finagolfin]

I'm afraid NDK r28* will not be the LTS release

Yes, we know it won't be: Fredrik is proposing that we switch to it anyway.

[thunder-coding]

lgtm in current shape. Also managed to build nodejs and nodejs-lts with little patchwork, so not bad, but I already had seen it coming. We might face build errors with packages that are using older C standards, as it seems like LLONG_MAX and other macros are now only enabled for newer C standards (-std=c11 and later)