. Use a better ALL_TARGET. Having check as part of it tried to install
some files. Use check-runs to achieve the desired testing without
doing any installation.
. ${INSTALL_MAN} -> ${INSTALL_DATA} for doc installation (they aren't
manual pages).
- Don't depend on math/libgmp-freebsd on FreeBSD <= 500023, use the base
libgmp instead. On FreeBSD > 500023 depend on math/libgmp4, as
math/libgmp-freebsd doesn't build on all architectures.
- Don't add PREFIX/include and PREFIX/lib to the search paths by default,
so on FreeBSD 4 the base libgmp is used. This protects from using one of
the libgmp ports if installed without registering a dependency on it.
- Keep from auto-detecting libgmp when WITHOUT_GMP is defined by specifying
the arithmetic to use.
Note: When using auto-detection and libgmp can't be found ndiff normally
would check for extended precision arithmetic first and succeed with it.
But using extended precision arithmetic causes the test suite to fail
(i.e. lots of differences) on all architectures expect sparc64. Therefore
specify double precision arithmetic for all other architectures when built
with WITHOUT_GMP.
Submitted by: marius
ndiff is a utility for comparing putatively similar files, ignoring small
numeric differences. The utility is written by Nelson H. F. Beebe and
covered by the GNU General Public License (GPL), version 2. It may be
built with arbitrary precision support (more powerful) or using built-in
floating point precision, see Makefile.
Assessing the consistency of a numerical program run in multiple
environments (operating systems, architectures, or compilers) can be a
difficult task for a human, as small differences in numerical output values
are expected. File differencing utilites, such as diff(1), will generally
produce voluminous output, often longer than the original files.
ndiff solves this problem. Taking two two text files expected to be
identical, or at least numerically similar, it allows to specify absolute
and/or relative error tolerances for differences between numerical values
in the two files, and then reports only the lines with values exceeding
those tolerances. It also tells by how much they differ. A simple example:
% ndiff --relative-error 1.0e-3 test019.txt.1 test019.txt.2
### Maximum relative error in matching lines = 8.64e-51 at line 129 field 4
WWW: http://www.math.utah.edu/~beebe/software/ndiff/
I've cleaned up the submitted version a little.
PR: 62221
Submitted by: Stefan A. Deutscher <sad@mailaps.org>
