gmp-4.1.3-rc1

[Torbjorn Granlund]

Roberto Bagnara <bagnara at cs.unipr.it> writes:

  $ gcc -DHAVE_CONFIG_H -I. -I/usr/local/distrib/gmp-4.1.3/mpz -I.. -D__GMP_WITHIN_GMP -I/usr/local/distrib/gmp-4.1.3 -g -O2 -fomit-frame-pointer -mcpu=athlon -march=athlon -c /usr/local/distrib/gmp-4.1.3/mpz/aorsmul.c
  `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
  /usr/local/distrib/gmp-4.1.3/mpz/aorsmul.c:44: error: conflicting types for '__gmpz_aorsmul'
  /usr/local/distrib/gmp-4.1.3/mpz/aorsmul.c:39: error: previous declaration of '__gmpz_aorsmul' was here
  /usr/local/distrib/gmp-4.1.3/mpz/aorsmul.c:44: error: conflicting types for '__gmpz_aorsmul'
  /usr/local/distrib/gmp-4.1.3/mpz/aorsmul.c:39: error: previous declaration of '__gmpz_aorsmul' was here
  
We will do something about that, either reject gcc 3.4.0 at
configure time, or work around this bug.

  It is a pity that --enable-cxx does not default to
  `yes' when an adequate C++ compiler is available.
  This means several other "bug reports" for those of us
  relying on the C++ interface.  What are the reasons behind
  the current default?  The C++ interface should somehow be
  out of its experimental phase.  Or not?

The language itself and the GMP C++ code has probably matured by
now, but the compilers still cause major headaches.  If we made
--enable-cxx the default, the result would be that GMP didn't
build for most users.

We might be able to design tests that reject many of the
compilers/include files/libraries that cause headaches.  But
that'd be a lot of work, and since C++ compiler writers are very
quick to break new things, wouldn't be successful unless we made
very frequent gmp releases.  :-)

--
Torbjörn