Date: Thu, 11 Jan 2007 09:48:54 +0900 (JST) From: NAKATA Maho <chat95@mac.com> To: ports@freebsd.org, portmgr@freebsd.org Subject: Linking against BLAS/LAPACK and optimized BLAS - ATLAS (was Re: Migration tips for gfortran42) Message-ID: <20070111.094854.115975485.chat95@mac.com> In-Reply-To: <20070111.094542.78764907.chat95@mac.com> References: <20070107.133544.78739935.chat95@mac.com> <20070109.175640.102530289.chat95@mac.com> <20070111.094542.78764907.chat95@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi here is some tips again
* Linking blas/lapack or atlas
.if exists(${LOCALBASE}/lib/libatlas_r.so) && !defined(WITH_BLAS)
WITH_ATLAS= yes
.endif
.if defined(WITH_ATLAS)
LIB_DEPENDS+= atlas.2:${PORTSDIR}/math/atlas
BLAS= -lf77blas -latlas
LAPACK= -lalapack
.else
LIB_DEPENDS+= blas.2:${PORTSDIR}/math/blas
LIB_DEPENDS+= lapack.4:${PORTSDIR}/math/lapack
BLAS_LIBS= -lblas
LAPACK= -lalapack
.endif
atlas build is very fragile and CPU/platform dependent. and
pointyhat doesn't build usually and I think atlas from packagecluster
can also be unusbale or low performance
for some cases (if you have 4 CPU and if package cluster have 2 CPU)
using LAPACK/BLAS is good for package building for casual users.
thanks,
-- NAKATA, Maho (maho@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070111.094854.115975485.chat95>