From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: lapack creates /lapack-3.0.6*
Date: Fri, 09 Jan 2009 17:06:00 -0000 [thread overview]
Message-ID: <20090109165122.GA16894@ednor.casa.cgf.cx> (raw)
In-Reply-To: <tv4cm49iks60k6oq2m9jd56k64osdvuksm@4ax.com>
On Thu, Jan 08, 2009 at 09:58:20AM -0500, Andrew Schulman wrote:
>I just upgraded to the latest lapack package, and found that I now have the
>following new files:
>
>$ ls -l /lapack*
>-rw-r--r-- 1 ASchulma Domain Users 49630 Mar 23 2006 /lapack-3.0-6.patch
>
>/lapack-3.0-6:
>total 4
>drwxr-xr-x 1 ASchulma Domain Users 0 Jan 8 09:50 CYGWIN-PATCHES/
>-rw-r--r-- 1 ASchulma Domain Users 2680 Mar 22 2006 Makefile
>drwxr-xr-x 1 ASchulma Domain Users 0 Jan 8 09:51 atlas-3.6.0/
>drwxr-xr-x 1 ASchulma Domain Users 0 Jan 8 09:51 cblas/
>drwxr-xr-x 1 ASchulma Domain Users 0 Jan 8 09:52 lapack-3.0/
>
>Please correct this.
Sorry for the inconvenience.
There really is no new lapack. I screwed up patching the binary tarball
to fix a problem so that the csh setup files dealt with pathnames with
spaces. Dropping back to 3.0-5 would have gotten you working, just in
case that wasn't obvious.
I've put my changes back and made a new 3.0-8 release, replacing the
stopgap version that Corinna had installed.
But don't expect any new functionality.
cgf
--
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/
prev parent reply other threads:[~2009-01-09 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 15:31 Andrew Schulman
2009-01-09 12:48 ` Corinna Vinschen
2009-01-09 17:06 ` Christopher Faylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090109165122.GA16894@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).