mirror/freebsd-ports
1
0
Fork 0
mirror of https://git.FreeBSD.org/ports.git synced 2024-12-23 04:23:08 +00:00
Code Issues Releases Activity
63fba1e668
freebsd-ports/math/ndiff/Makefile

63 lines
1.4 KiB
Makefile
Raw Normal View History

Add a port of ndiff: 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>
2004-02-18 22:02:39 +00:00
# New ports collection makefile for: ndiff
# Date created: 31 January 2004
# Whom: Stefan A. Deutscher (sad@mailaps.org)
#
# $FreeBSD$
#
PORTNAME= ndiff
PORTVERSION= 2.00
Chase gmp library and bump PORTREVISION.
2006-05-10 14:46:47 +00:00
PORTREVISION= 2
Add a port of ndiff: 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>
2004-02-18 22:02:39 +00:00
CATEGORIES= math
MASTER_SITES= ftp://ftp.math.utah.edu/pub/misc/
PKGNAMEPREFIX=
MAINTAINER= ports@FreeBSD.org
COMMENT= Compare putatively similar files, ignoring small numeric differences
Deal with the libgmp dependency properly: - 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
2004-06-02 17:18:39 +00:00
.include <bsd.port.pre.mk>
Add a port of ndiff: 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>
2004-02-18 22:02:39 +00:00
.if !defined(WITHOUT_GMP)
Deal with the libgmp dependency properly: - 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
2004-06-02 17:18:39 +00:00
.if ${OSVERSION} > 500023
Chase gmp library and bump PORTREVISION.
2006-05-10 14:46:47 +00:00
LIB_DEPENDS= gmp.7:${PORTSDIR}/math/libgmp4
Deal with the libgmp dependency properly: - 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
2004-06-02 17:18:39 +00:00
CFLAGS+= -I${LOCALBASE}/include
LDFLAGS+= -L${LOCALBASE}/lib
.endif
CONFIGURE_ARGS= --with-gmp
CONFIGURE_ENV= CFLAGS="${CFLAGS}" LDFLAGS="${LDFLAGS}"
.else
.if ${ARCH} == sparc64
CONFIGURE_ARGS= --with-long-double
.else
CONFIGURE_ARGS= --with-double
.endif
Add a port of ndiff: 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>
2004-02-18 22:02:39 +00:00
.endif
GNU_CONFIGURE= yes
. Respect hier(7). . 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).
2004-12-16 07:08:25 +00:00
ALL_TARGET= all check-runs
Add a port of ndiff: 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>
2004-02-18 22:02:39 +00:00
MAN1= ndiff.1
.if !defined(NOPORTDOCS)
PORTDOCS= *
.endif
. Respect hier(7). . 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).
2004-12-16 07:08:25 +00:00
post-patch:
@${REINPLACE_CMD} -e "s:%%DATADIR%%:${DATADIR}:g" ${WRKSRC}/Makefile.in
Add a port of ndiff: 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>
2004-02-18 22:02:39 +00:00
post-build:
@${ECHO_MSG} "If there were no errors in the above checks then type"
@${ECHO_MSG}
@${ECHO_MSG} " ${MAKE} install"
@${ECHO_MSG}
@${ECHO_MSG} "to install ${PORTNAME}-${PORTVERSION}"
post-install:
.if !defined(NOPORTDOCS)
${MKDIR} ${DOCSDIR}
. Respect hier(7). . 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).
2004-12-16 07:08:25 +00:00
${INSTALL_DATA} ${WRKSRC}/${PORTNAME}.pdf ${DOCSDIR}
${INSTALL_DATA} ${WRKSRC}/${PORTNAME}.ps ${DOCSDIR}
${INSTALL_DATA} ${WRKSRC}/${PORTNAME}.html ${DOCSDIR}
Add a port of ndiff: 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>
2004-02-18 22:02:39 +00:00
.endif
Deal with the libgmp dependency properly: - 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
2004-06-02 17:18:39 +00:00
.include <bsd.port.post.mk>
Reference in New Issue Copy Permalink