From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: What's the official state of Python module scipy in Cygwin?
Date: Sun, 21 Jun 2020 21:47:27 +0200 [thread overview]
Message-ID: <07f31ec7-0107-1d47-ac74-271a4cd200d7@gmail.com> (raw)
In-Reply-To: <15e60aa4-000e-2d15-7704-186d594fbfd4@SystematicSw.ab.ca>
On 21.06.2020 21:36, Brian Inglis wrote:
> On 2020-06-21 12:31, My Name via Cygwin wrote:
>> (M.A., I've figured out how to reply to the Cygwin Mailing List on these.
>> If you'd like me to remove your name from the list of addressees in my
>> future emails, please let me know? I have not found comprehensive docs for
>> this mailing-list software, so I'm clueless.)
>>
>
>> Going by an old memory of mine, I recall that parts of Scipy rely on BLAS,
>> https://en.wikipedia.org/wiki/Basic_Linear_Algebra_Subprograms, and I read
>> somewhere that that dependency adds to the difficulty of porting Scipy to
>> new platforms.
> Try installing or upgrading liblapack-devel liblapack-doc libopenblas
> openblas-doc and see how far that gets you.
> I remember coming across atlas elsewhere, but only know it provides some tuned
> BLAS and LAPACK routines.
>
if Scipy requires just a BLAS, liblapack-devel should be enough for
the compilation.
libopenblas for compatibility reason provides only the shared library
but I am not packing the headers. It helps to run faster any BLAS
routine used by programs.
ATLAS takes too long to compile and it does NOT provides multiprocessor
libraries as OpenBlas. So no interest to package it for Cygwin from
my side.
Regards
Marco
next prev parent reply other threads:[~2020-06-21 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 13:03 My Name
2020-06-21 17:51 ` Marco Atzeri
2020-06-21 18:31 ` My Name
2020-06-21 19:36 ` Brian Inglis
2020-06-21 19:47 ` Marco Atzeri [this message]
2020-06-21 22:47 ` My Name
2020-06-21 23:28 ` My Name
2020-06-21 19:40 ` Eliot Moss
2020-06-21 21:09 ` Marco Atzeri
2020-06-21 23:16 ` My Name
2020-06-22 2:38 ` My Name
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=07f31ec7-0107-1d47-ac74-271a4cd200d7@gmail.com \
--to=marco.atzeri@gmail.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).