Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <20050928181443.31915.qmail@web31510.mail.mud.yahoo.com>
Date: Wed, 28 Sep 2005 11:14:43 -0700 (PDT)
From: "James R. Phillips" <antiskid56-cygwin AT yahoo DOT com>
Reply-To: antiskid56-cygwin AT yahoo DOT com
Subject: Re: cygblas.dll not found (lapack)
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

>Is there some reason that lapack can't put cygblas.dll into /usr/bin
>instead of /usr/lib/lapack? 

Yes, and I'm glad you asked that.

The lapack package is designed to facilitate the build/installation of locally
optimized lapack/blas libraries using atlas, which is included in the lapack
source package.  After building the optimized libs, they should be installed in
/usr/local/bin, which precedes /usr/lib/lapack in the default path.

There was a discussion on cygwin-apps to arrive at this design approach, which
ensures that a new lapack binary package can be installed without over-writing
or over-riding the locally optimized dll's.  Offhand, I'm don't recall why it
was decided that /usr/lib/lapack would be better than /usr/bin, since
/usr/local/bin precedes both of them in the default path.  Possibly that
decision should be revisited.

In any case, I am very interested in receiving install reports from those who
wish to build/install locally optimized lapack/blas libraries using atlas. 
Install lapack source, and follow the instructions in
lapack-3.0-2/CYGWIN-PATCHES/README.optimize should you wish to try this.  Note
that several hours compile time is typically required for atlas to perform its
optimization process.

Thanks,

jrp


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/