Message-ID: <100169.29656.qm@web25507.mail.ukl.yahoo.com>
Date: Fri, 8 Jan 2010 20:31:41 +0000 (GMT)
From: Marco Atzeri <marco_atzeri@yahoo.it>
Subject: Re: [ANNOUNCEMENT] updated: orpie-1.5.1-2
To: cygwin@cygwin.com, Andy Koppe <andy.koppe@gmail.com>
In-Reply-To: <416096c61001081142m4bc6f5b7saf93877f2ad3935@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

--- Ven 8/1/10, Andy Koppe ha scritto:

> 2010/1/8 Andrew Schulman:
> > * In order for lapack to work, you have to have
> /usr/lib/lapack in your
> > $PATH. =A0IMO that's a bug
>=20
> I agree, and I shudder to think what the path would look
> like if every
> library did that. I don't see why the lapack DLLs can't go
> into
> /usr/bin like everything else.

because it is possible to have on top of the standard=20
blas/lapack the specialized ATLAS version for the
specific processor.

Putting the dll's in /usr/lib/lapack
and adding that at the end of PATH allows
to put the atlas versions in /usr/lib=20
and they will take precedence over the PATH.

On other unix systems this can be managed with=20
symbolic links but on windows is it not possible.
The workaround was defined by the previous lapack=20
mantainer James R. Phillips and I decided maintain it.

>=20
> Thanks for the fix.
>=20
> Andy
>=20


Regards
Marco


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