pkgsrc/math/mpfr, branch pkgsrc-

Updated mpfr to 3.1.6.

2017-09-10T21:17:02Z

Changes from version 3.1.5 to version 3.1.6: - Improved MPFR manual. - Bug fixes (see and ChangeLog file). - Autotools: Under Linux, make sure that the old dtags (when supported) are used if LD_LIBRARY_PATH is defined; otherwise "make check" would check an installed, compatible MPFR library found in LD_LIBRARY_PATH instead of the one that has been built with "make".

Hack the pkg to at least build + install on NetBSD/alpha - may need

2017-08-30T10:35:54Z

revisiting after closer examination of the underlying issues.

Updated mpfr to 3.1.5.

2016-10-03T12:35:18Z

Changes from version 3.1.4 to version 3.1.5: - C++11 compatibility. - Bug fixes (see and ChangeLog file). - More tests.

Update mpfr to 3.1.4:

2016-03-08T15:03:42Z

Changes from version 3.1.3 to version 3.1.4: - Improved MPFR manual. - Bug fixes (see and ChangeLog file). - MinGW (MS Windows): Added support for thread-safe DLL (shared library).

Add SHA512 digests for distfiles for math category

2015-11-03T23:33:26Z

Problems found locating distfiles: Package dfftpack: missing distfile dfftpack-20001209.tar.gz Package eispack: missing distfile eispack-20001130.tar.gz Package fftpack: missing distfile fftpack-20001130.tar.gz Package linpack: missing distfile linpack-20010510.tar.gz Package minpack: missing distfile minpack-20001130.tar.gz Package odepack: missing distfile odepack-20001130.tar.gz Package py-networkx: missing distfile networkx-1.10.tar.gz Package py-sympy: missing distfile sympy-0.7.6.1.tar.gz Package quadpack: missing distfile quadpack-20001130.tar.gz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.

Don't clean intermediate files after checksum/patch phase.

2015-09-15T20:56:33Z

The work directories are almost empty, so it doesn't save much space. It makes debugging annoying and it breaks local DISTDIR settings.

Update to 3.1.3

2015-06-30T10:25:01Z

Changelog: Changes from version 3.1.2 to version 3.1.3: - Better support for Automake 1.13+ (now used to generate the tarball). - Improved MPFR manual. - Bug fixes (see and ChangeLog file).

Apply 11 upstream patches, bump to 3.2.1pl11.

2014-12-05T13:16:26Z

Requested by Kai-Uwe Eckhardt. Remove an incorrect comment. Changes: One of the mpfr_exp implementations uses a left shift on an integer that can be negative: exps <<= 1; and this has an undefined behavior according to the ISO C standard. In most cases, this will correspond to a multiplication by 2, and the code will behave as expected (this is why the bug hadn't been detected until now). But problems may occur if a sanitizer is used (this is how this bug was detected) or possibly in case of advanced optimizations, such as LTO. This is fixed by the exp_2 patch. The mpfr_fits_u*_p functions return 0 ("doesn't fit") instead of non-zero ("fits") on negative arguments for which the rounding to an integer in the given rounding mode is 0. This bug is fixed by the fits-smallneg patch, which also updates the testcases. Some tget_flt tests fail in environments where native C floating-point division by zero is not supported, e.g. regarded as an error, such as with Clang's sanitizer; some similar tests were already disabled in such a case, but not all. The tset_ld test triggers a useless overflow on a double. These problems are fixed by the clang-divby0 patch, which also disables constant division by zero on the native C type double with Clang in order to avoid incorrect code. The formatted output functions (mpfr_*printf) are incorrect on the value 0 when using the alternative form (# flag), a positive precision, and the g or G conversion specifier: there is one additional trailing 0. The corresponding test is also incorrect (explaining why the bug was not detected). These problems are fixed by the printf-alt0 patch, which also provides some additional related tests. Only for applications using the custom interface: The mpfr_custom_init_set macro has a typo in a variable name, which can yield incorrect behavior if the second argument is not a simple expression. This bug is fixed by the custom_init_set patch. The build fails on li2.c with the GCC -Werror=return-type option when logging has been enabled. This problem is fixed by the li2-return patch. The rounding of mpfr_exp can be incorrect for output precisions larger than or equal to MPFR_EXP_THRESHOLD (several thousands of bits; its value depends on the architecture). This bug is fixed by the exp3 patch, which also provides a testcase. This MPFR release fails to build with GMP 6 when the --with-gmp-build configure option is used. The gmp6-compat patch fixes this compatibility problem. When dividing a very large number (near the maximum finite one, in absolute value) by a very small number (near the minimum one, in absolute value), an integer overflow occurs in the computation of the exponent of the result, yielding undefined behavior, such as the result 0 instead of infinity. This bug is fixed by the div-overflow patch, which also provides a testcase. The vasprintf.c source file contains incorrect assertions, which may fail while the computation is valid; this can occur only when outputting tiny numbers (very small exponents). These assertions are fixed by the vasprintf patch, which also provides a testcase. A buffer overflow may occur in mpfr_strtofr. This is due to incorrect GMP documentation for mpn_set_str about the size of a buffer (discussion; first fix in the GMP documentation). This bug is present in the MPFR versions from 2.1.0 (adding mpfr_strtofr) to this one, and can be detected by running "make check" in a 32-bit ABI under GNU/Linux with alloca disabled (this is currently possible by using the --with-gmp-build configure option where alloca has been disabled in the GMP build). It is fixed by the strtofr patch.

Mark two custom targets .PHONY.

2014-12-05T13:14:21Z

XXX: This does not handle distribution patches.

Reset maintainer for resigned developers.

2013-12-23T11:57:02Z