[gmp] Fix building for linux x86

[robbert-ef]

• Changes comply with the maintainer guide
• SHA512s are updated for each updated download
• The "supports" clause reflects platforms that may be fixed by this new version
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[robbert-ef]

@microsoft-github-policy-service agree company="Easyflex"

[dg0yt]

I have recently seen/used the same x86 pattern in another port but for Android.

• Do we really need ABI=32 in addition to -m32?
• Which other x86 toolchains/triplets will understand -m32?
• Can we get -m32 from the cmake toolchain?

[robbert-ef]

ABI=32 is required, fixes:

configure: error: Oops, mp_limb_t is 32 bits, but the assembler code
in this configuration expects 64 bits.
You appear to have set $CFLAGS, perhaps you also need to tell GMP the
intended ABI, see "ABI and ISA" in the manual.

The -m32 is also necessary, without it, compile of asm fails:

tmp-add_n.s: Assembler messages:
tmp-add_n.s:202: Error: operand type mismatch for `jmp'
make[2]: *** [add_n.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
tmp-sub_n.s: Assembler messages:
tmp-sub_n.s:202: Error: operand type mismatch for `jmp'
make[2]: *** [sub_n.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

[Neumann-A]

If you need asm flags you might want to actually request it from vcpkg_get_cmake_vars.

[dg0yt]

Unfortunately, vcpkg_cmake_get_vars isn't taking parameters such as LANGUAGES ATM. (And maybe it should be handled gracefully if ASM can't be enabled.)