To use the autotools:

$ libtoolize
$ autoheader
$ aclocal
$ automake -c -a
$ autoconf
$ ./configure --with-gmp=<directory_where_gmp_is_installed>
$ make
$ make check

Alternatively, you can simply type:

$ autoreconf -i
$ ./configure --with-gmp=<directory_where_gmp_is_installed>
$ make
$ make check

Warning: only configure.ac and Makefile.am should be in cvs
	(the other files are automatically generated)

##############################################################################

Documentation:

- ecm.xml was generated from ecm.1 using doclifter-2.1
  ./doclifter < ecm.1 > ecm.xml
  (http://en.tldp.org/HOWTO/DocBook-Demystification-HOWTO/x181.html
   http://www.catb.org/~esr//doclifter/)
  See the documentation of ROX-Filer (http://rox.sf.net/) for example
	(see rox/ROX-Filer/src/Docs/Manual.xml).

- to generate ecm.html:
  $ xsltproc -o ecm.html $XSLDIR/html/docbook.xsl ecm.xml
  where XSLDIR is the directory where docbook stylesheets are installed
  (e.g. /usr/share/sgml/docbook/xsl-stylesheets-1.65.1-1)

- to generate man format:
  $ xsltproc -o ecm.1 $XSLDIR/manpages/docbook.xsl ecm.xml
  (or "xmlto man ecm.xml")

- to generate pdf:
  $ xmlto pdf ecm.xml

Note: we currently keep ecm.1 in the repository, even though it is a 
generated file and not a source. This is to avoid having a dependency
on xsltproc and docbook in every build; these tools are not usually
installed by default in distributions. It does not seem to be possible
to set up the Makefile so ecm.1 is required only for "make install" and
"make dist". We need to list ecm.1 in one of the automake _MANS primaries 
to get it installed in the proper man page directory, and when it is 
listed in any _MANS primary, it is automatically added to the "am-all" 
target which is processed by "make" or "make all".

##############################################################################

To make a new release:

  0) Check all tests pass (make check and make longcheck),
     with or without NTT (./test.ecm "./ecm -no-ntt"),
     with or without --enable-openmp,
     check the issues in TODO, and for issues on gitlab.inria.fr/zimmerma/ecm.
     Check no compiler warnings remain (with and without assertions),
        if possible with different compilers (gcc, clang, llvm-gcc, ...)
     Check "make longcheck" works with --enable-valgrind-tests.
     Check that configure works outside the source directory
        (from the tarball).
     Check the default tuning files */params.h (see the main
     file ecm-params.h) on different platforms with "make ecm-params"
     Compare the efficiency wrt the previous release with "./ecm 1e6 < c270"
     and "./ecmbench ./ecm".
  1) Check the version (configure.ac and build.vs/gen_ecm_h.bat).
     Switch assertions to off by default in configure.ac.
  2) Update the NEWS file, and check the INSTALL-ecm file is up-to-date.
  3) no need to update ChangeLog anymore, it points to "git log"
  4) Check the required sizes of P-1, P+1, ECM champions in champions.h.
  5) Generate the release version with "make dist".
  6) Test the release version with "make distcheck" (in particular, check
     the man page is correctly installed). You might need to redefine
     LD_LIBRARY_PATH so that the system libgmp is used.
  7) Check the man page (ecm.1) is up to date.
     Update version-info in Makefile.am if needed.
  8) Check factors are really found using the checkprob and tools/check.sage
     programs, for example to estimate the average number of curves to find
     a 20-digit prime with B1=11000 and -param 1:
     $ ./checkprob "./ecm -param 1" 31622776601683800097 11000
     $ ./checkprob "./ecm -param 0" 3162277660168380112437259 50000 # 25d
     and with check.sage, the following command checks the ./ecm binary
     for all parametrizations (-param 0-3), with B1=11000 and B2=1873422,
     and all sigma values < 1000, and checks the prime 31622776601683800097
     is found when it should be (i.e., when the group order is (B1,B2)-smooth):
     check_found_all ("./ecm", 31622776601683800097, 11000, 1873422, 1000)
  9) If there is no problem, add a tag to the version corresponding to the
     release, for example:
     $ git tag -a 7.0.4 fcc8509
     $ git push

     Version     svn tag     git tag
     6.0.1       r781        1a2f3c6
     6.2         r1290       1fb9bfa
     6.2.1 	 r1307       b600e50
     6.3	 r1501	     b3451db
     6.4	 r1672	     468d182
     6.4.1	 r1844	     1a2d08a
     6.4.2	 r1882	     69fd89d
     6.4.3	 r2100	     f8c244d
     6.4.4	 r2439	     2f06a62
     7.0	 r2900	     2ffe6f9
     7.0.1	 r2932	     cd57d0b
     7.0.2	 r2961	     4dcc4fc
     7.0.3	 r2963	     ee145f2
     7.0.4	 r2991	     fcc8509
     7.0.5                   0ab79ad
     7.0.6                   0befa9a

 10) increase the version number in configure.ac and build.vs/gen_ecm_h.bat,
     and switch assertions to on by default in configure.ac.

To see the differences between a given tag and the current version:

$ git diff 7.0.4

To put the release on gitlab, see howto-gitlab-making-releases.txt.