gmp 6.3.0, mpc 1.3.1, mpfr 4.2.1, mpfrcx 0.6.3, gmpy2 2.2.0a1

[mkoeppe]

The unreleased 2.2.x series has work on support for Python 3.12

https://github.com/aleaxit/gmpy

The new version makes it necessary to tighten the requirements for MPC and MPFR.
We do the version check without pkg-config as before; changing it to pkg-config is #31348.

(The upgrade of the packages was previously done in #36775, but has now been merged here.)

📝 Checklist

• The title is concise, informative, and self-explanatory.
• The description explains in detail what this PR is about.
• I have linked a relevant issue or discussion.
• I have created tests covering the changes.
• I have updated the documentation accordingly.

⌛ Dependencies

[tornaria]

FWIW, we are shipping 2.2.0a1 in void linux since september. This supports python 3.12 and is available on pypi: https://pypi.org/project/gmpy2/2.2.0a1/

[mkoeppe]

Thanks @tornaria, I'll try switching to this release!

[mkoeppe]

Full tests at https://github.com/mkoeppe/sage/actions/runs/7205490817

debian-bullseye has MPC 1.2.0, which passes my test in spkg-configure but is rejected by gmpy2 (it needs 1.2.1).

[dimpase]

we can as we often do get the MPC version from mpc.h - akin to what we do for NTL 😭

/* Define MPC version number */
#define MPC_VERSION_MAJOR 1
#define MPC_VERSION_MINOR 3
#define MPC_VERSION_PATCHLEVEL 1
#define MPC_VERSION_STRING "1.3.1"

/* Macros dealing with MPC VERSION */
#define MPC_VERSION_NUM(a,b,c) (((a) << 16L) | ((b) << 8) | (c))
#define MPC_VERSION                                                     \
  MPC_VERSION_NUM(MPC_VERSION_MAJOR,MPC_VERSION_MINOR,MPC_VERSION_PATCHLEVEL)

a bit shorter than NTL code will use MPC_VERSION - which is 66049 for 1.2.1

[mkoeppe]

I'm just copying the test from gmpy.h

[dimpase]

Do you mean AC_RUN_ and not AC_LINK_?!

[mkoeppe]

No

[mkoeppe]

This is a compile-time test

[dimpase]

It's AC_COMPILE_ then.

Also not clear how you make sure to test for -lmpc, as you took AC_SEARCH_LIBS out.

[mkoeppe]

I'll get back to it later when I have a bit more time. Feel free to push a fix

[dimpase]

ready now, I think

[mkoeppe]

Thanks. I've switched the lib test to use a newer function, like I did previously in 109671e

[mkoeppe]

With the gmpy2 upgrade here, passes all tests on the same machine where I reproduced the failures reported in #36775 (comment) with the old gmpy2.

[github-actions]

Documentation preview for this PR (built with commit 4bdb76d; changes) is ready! 🎉

[mkoeppe]

All tests passed, let's get this in.

[saraedum]

if conda tests fail, we need to make sure this gmpy2 version (released on PyPI) makes it to Conda quickly.

Note that conda usually does not package alphas. Is the alpha absolutely necessary now? Does anything break badly if I just install sagelib with gmpy 2.1.x?

[mkoeppe]

Check what's declared in build/pkgs/gmpy2/install-requires.txt build/pkgs/gmpy2/version_requirements.txt

[saraedum]

It says gmpy2 ~=2.1.b999. Which means yes. Though that . before the b confuses me.

[mkoeppe]

This should accept all 2.1.x versions, or at least so I claimed in the 4bdb76d commit.

[mkoeppe]

Though that . before the b confuses me.

Right, that's not normalized