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 18:17:04 +0100 [thread overview]
Message-ID: <idjio2384bz.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <idjpowb8hah.fsf@bimsb-sys02.mdc-berlin.net>
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> 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 dropped the flag and noticed that OpenBLAS is not mentioned at all (it
does retain a reference, but that’s expected when “openblas” is among
the inputs), so I also dropped “openblas” from the inputs and R built
just fine.
It’s a bit sad to me that we won’t be able to just use this BLAS
implementation, but if it fixes the build on ARM and MIPS I’m all for
it.
I can also confirm that dropping openblas from the R build “fixes” the
segfault when running
x <- eigen(crossprod(matrix(rnorm(50 * 500), 50, 500)))
as reported here: https://github.com/xianyi/OpenBLAS/issues/703
So, I think it’s a good idea to build R without OpenBLAS on all
architectures for now.
~~ Ricardo
next prev parent reply other threads:[~2016-02-05 17:17 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 ` R Ricardo Wurmus
2016-02-05 17:17 ` Ricardo Wurmus [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=idjio2384bz.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.