From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: R
Date: Fri, 5 Feb 2016 13:37:10 +0100 [thread overview]
Message-ID: <idjpowb8hah.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20160205100040.GA4213@debian.eduroam.u-bordeaux.fr>
Andreas Enge <andreas@enge.fr> writes:
> I did get a reply, but not using R, I do not quite know what to make of it:
> https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16697
> It would be nice if someone using R could help me out; if you send me an
> ssh key, I could give you access to an arm machine.
>
> To start, a probably simple question: Why do we use "--with-blas=openblas"?
I did this when we switched from ATLAS to OpenBLAS (for substitutability
reasons). It is possible I have misunderstood the meaning of this
configure flag.
Here’s the installation manual on building with a specific BLAS
implementation:
https://cran.r-project.org/doc/manuals/r-release/R-admin.html#BLAS
According to this section,
“R can make use of enhanced BLAS (Basic Linear Algebra Subprograms,
http://www.netlib.org/blas/faq.html) routines. However, these have
to be explicitly requested at configure time: R provides an internal
BLAS which is well-tested and will be adequate for most uses of R.”
There’s a separate section for OpenBLAS, which also mentions that using
a “shared BLAS” is a preferred alternative to linking with a particular
BLAS implementation. We already pass “--enable-BLAS-shlib”, so we
actually do use a shared BLAS, IIUC.
I guess we could drop the “--with-blas” flag and see if that helps. I
remember struggling with this a lot in the past. I’ll try building R
again without that flag and see if it still works.
I’m sorry if that’s what’s responsible for the failures, but it’s pretty
hard for me to understand how linking with a high-performance BLAS
implementation could have caused these build/test failures on other
platforms. I’ll report back when I have a successful build or an
interesting failure to share.
~~ Ricardo
next prev parent reply other threads:[~2016-02-05 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 19:39 R Andreas Enge
2016-02-05 10:00 ` R Andreas Enge
2016-02-05 10:55 ` R Pjotr Prins
2016-02-05 12:37 ` Ricardo Wurmus [this message]
2016-02-05 17:17 ` R Ricardo Wurmus
2016-02-05 17:59 ` R Kyle Meyer
2016-02-05 19:02 ` R Andreas Enge
2016-02-05 19:54 ` R Andreas Enge
2016-02-05 20:48 ` R Ricardo Wurmus
2016-02-05 22:24 ` R Andreas Enge
2016-09-08 11:41 ` R Ben Woodcroft
2016-09-08 13:02 ` R Ricardo Wurmus
2016-09-09 12:07 ` R Ben Woodcroft
2016-09-08 17:01 ` R Pjotr Prins
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=idjpowb8hah.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).