pkgsrc/math/slatec/Makefile

# $NetBSD: Makefile,v 1.20 2009/02/22 14:15:28 asau Exp $
#

DISTNAME=	slatec_src
PKGNAME=	slatec-4.1
PKGREVISION=	2
CATEGORIES=	math
MASTER_SITES=	${MASTER_SITE_NETLIB:=slatec/}
EXTRACT_SUFX=	.tgz

MAINTAINER=	adam@NetBSD.org
HOMEPAGE=	http://www.netlib.org/slatec/
COMMENT=	Library of mathematical and statistical Fortran 77 subroutines

WRKSRC=			${WRKDIR}/src
USE_LANGUAGES=		fortran
USE_LIBTOOL=		YES

INSTALLATION_DIRS=	lib

post-extract:
	cd ${FILESDIR} && cp d1mach.f i1mach.f r1mach.f ${WRKSRC}

.include "../../mk/bsd.pkg.mk"
Use MASTER_SITE_NETLIB for Netlib and its mirrors. Discussed with Tobias Nygren. 2009-02-22 15:15:28 +01:00			`# $NetBSD: Makefile,v 1.20 2009/02/22 14:15:28 asau Exp $`
Now uses libtool and builds shared libraries 2003-12-04 16:10:48 +01:00			`#`
Initial import of new "slatec" package: Library of mathematical and statistical Fortran 77 subroutines 2000-11-28 01:26:53 +01:00
			`DISTNAME= slatec_src`
			`PKGNAME= slatec-4.1`
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10 in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include. 2004-10-03 02:12:51 +02:00			`PKGREVISION= 2`
Initial import of new "slatec" package: Library of mathematical and statistical Fortran 77 subroutines 2000-11-28 01:26:53 +01:00			`CATEGORIES= math`
Use MASTER_SITE_NETLIB for Netlib and its mirrors. Discussed with Tobias Nygren. 2009-02-22 15:15:28 +01:00			`MASTER_SITES= ${MASTER_SITE_NETLIB:=slatec/}`
Initial import of new "slatec" package: Library of mathematical and statistical Fortran 77 subroutines 2000-11-28 01:26:53 +01:00			`EXTRACT_SUFX= .tgz`

Now uses libtool and builds shared libraries 2003-12-04 16:10:48 +01:00			`MAINTAINER= adam@NetBSD.org`
			`HOMEPAGE= http://www.netlib.org/slatec/`
Update to new COMMENT style: COMMENT var in Makefile instead of pkg/COMMENT. 2001-02-17 18:52:59 +01:00			`COMMENT= Library of mathematical and statistical Fortran 77 subroutines`
Initial import of new "slatec" package: Library of mathematical and statistical Fortran 77 subroutines 2000-11-28 01:26:53 +01:00
Move WRKSRC definition away from the first paragraph in a Makefile. 2004-01-20 13:18:15 +01:00			`WRKSRC= ${WRKDIR}/src`
Nuke USE_FORTRAN and bring the f2c handling within the mk/compiler framework. The list of changes include: * Modify compiler.mk so that "c" is always prepended to USE_LANGUAGES, so we no longer need to say it in package Makefiles. Packages should now append to USE_LANGUAGES instead of setting it. * Create mk/compiler/f2c.mk which implements another pseudo-compiler "f2c" that may be used with any C compiler backend, e.g. PKGSRC_COMPILER= f2c ccache gcc * Teach the various "real" compiler files, e.g., sunpro.mk, mipspro.mk, etc., to use f2c if the native Fortran compiler isn't present. Packages that use Fortran should now simply include the line: USE_LANGUAGES+= fortran in the package Makefile. 2005-01-12 16:31:58 +01:00			`USE_LANGUAGES= fortran`
Now uses libtool and builds shared libraries 2003-12-04 16:10:48 +01:00			`USE_LIBTOOL= YES`
Initial import of new "slatec" package: Library of mathematical and statistical Fortran 77 subroutines 2000-11-28 01:26:53 +01:00
Prepare for switching to NO_MTREE=yes. 2007-03-24 20:21:18 +01:00			`INSTALLATION_DIRS= lib`

Added machine parameter files from the BLAS. Use different optimization based on compiler, and add "-lg2c -lm" to link if using g77, "-lm" otherwise. 2001-01-20 22:25:31 +01:00			`post-extract:`
When all source files are compiled with a Fortran compiler, why should a C compiler be used for linking them? 2006-07-27 20:49:47 +02:00			`cd ${FILESDIR} && cp d1mach.f i1mach.f r1mach.f ${WRKSRC}`
Initial import of new "slatec" package: Library of mathematical and statistical Fortran 77 subroutines 2000-11-28 01:26:53 +01:00
			`.include "../../mk/bsd.pkg.mk"`