Re: [Rd] openblas

2019-05-07 Thread Dirk Eddelbuettel
On 7 May 2019 at 19:43, Peter Langfelder wrote: | (CCing the R-devel list, maybe someone will have a better answer.) | | To be honest, I don't know how to. I wasn't able to configure R to use | OpenBLAS using the configure script and options on my Linux Fedora system. | I configure it without ex

Re: [Rd] openblas

2019-05-07 Thread Peter Langfelder
(CCing the R-devel list, maybe someone will have a better answer.) To be honest, I don't know how to. I wasn't able to configure R to use OpenBLAS using the configure script and options on my Linux Fedora system. I configure it without external BLAS, then replace the libRblas.dylib (.so in my case

Re: [Rd] openblas

2019-05-07 Thread Peter Langfelder
I'm a linux guy so take the advice with a grain of salt... When you run the configure script, look at the output at the end of the run, it should either say Options enabled: shared BLAS, ... (means you are using R BLAS) or it should mention OpenBLAS in External libraries (meaning you

[Rd] openblas

2019-05-07 Thread robin hankin
Hello, macosx 10.13.6, Rdevel r76458 I'm trying to compile against openblas to reproduce an error on the CRAN check page (my package is clean under winbuilder and all but one of the checks). I've downloaded and installed openblas 0.3.7 but I am not 100% sure that it is being used by R. Using

Re: [Rd] Staged installation fail on some file systems

2019-05-07 Thread Henrik Bengtsson
On Tue, May 7, 2019 at 9:05 AM Tomas Kalibera wrote: > > Thanks for the report. According to my reading, this use of "mv" is ok > and the renameat2() call which the invocation of "mv" leads to is also > ok and allowed by POSIX in this context. It could only fail with EEXIST > if the target direct

Re: [Rd] Staged installation fail on some file systems

2019-05-07 Thread Tomas Kalibera
Thanks for the report.  According to my reading, this use of "mv" is ok and the renameat2() call which the invocation of "mv" leads to is also ok and allowed by POSIX in this context. It could only fail with EEXIST if the target directory (path/pkg) was not empty. So far I've not been able to r

Re: [Rd] Strange error messages from parallel::mcparallel family under 3.6.0

2019-05-07 Thread Tomas Kalibera
Thanks, fixed in R-devel and R-patched. The error happens in the child process when it is already exiting, after it had delivered a result, so this should not cause any trouble in an unpatched version of R (apart from showing that message). It is specific to mccollect(wait=FALSE). Best Tomas