The GMP project uses Mercurial for its revision control. Mercurial is a distributed SCM, where each checkout is just another repository. Where the central repository lives is just an agreement between developers, not something Mercurial enforces.

Once you have Mercurial installed, do

hg clone https://gmplib.org/repo/gmp/ TARGDIR

for the unstable development version, or

hg clone https://gmplib.org/repo/gmp-6.2/ TARGDIR

for the current patch level of GMP 6.2.

A list of all repositories we publish are available at gmplib.org/repo/.

See also the Mercurial quickstart guide.

Once you have your own repository, you need to generate some build files. Perhaps the script .bootstrap works out-of-the box; if it doesn't, you need to install automake (at least version 1.11.6) and autoconf (at least version 2.59) and then try .bootstrap again. You may safely ignore the 4 lines of warnings from libtoolize.

Do not use autoreconf; it will overwrite config.guess which in turn will cause any builds to be awful.

Now you should be able to build GMP as usually, i.e., with

configure OPTIONS
make
make check

Usage conditions

These resources are open to the public, but we expect them to be used responsibly. Repeated clone command should be avoided. Scripting of clone commands is strongly discouraged.

As a guideline, more than one clone command per day is considered excessive. More than 10 is considered abuse, and if you sustain such a clone rate or significantly exceed it in a single day, your IP address will get a dishonorary mention in our firewall's block list.

There is really no good reason to repeat a clone command, except if you lost all previous copies. If you clone and then make local changes, they are easy to back out. And you can always clone from your own "master" clone.