Dirk
Thanks for a very helpful reply. I'll simplify my return values.
I mentioned Intel with rhub2 in my earlier post here, but I'm sorry
that was somewhat buried. Debugging is somewhere between painful and
impossible when my only check is submitting to CRAN!
Also, I had tried valgrind, but that
Hi
A couple of days ago I posted on R-package-devel about a mysterious
segfault from R CMD checks of my package secrdesign (see
https://CRAN.R-project.org/package=secrdesign, and
https://github.com/MurrayEfford/secrdesign) The issue rises only on
CRAN and only with the Intel(R) oneAPI DPC++/C++
My mistake - the SystemRequirements line had been lost from my DESCRIPTION
file (editing error?). OK and wiser now.
Sorry for wasting your time.
Murray
On Sun, Jun 24, 2018 at 3:59 AM, Murray Efford
wrote:
> Thanks for the advice. It seems that R CMD check (locally and on
> winbuilder)
.
I suspect Jeff's suggestion, to omit, does not apply to RcppParallel.
On Sun, Jun 24, 2018 at 3:31 AM, Dirk Eddelbuettel wrote:
>
> On 24 June 2018 at 03:22, Murray Efford wrote:
> | The RcppParallel introduction at https://rcppcore.github.io/
> RcppParallel/
> | instructs
The RcppParallel introduction at https://rcppcore.github.io/RcppParallel/
instructs package writers to include a Makevars file with
PKG_LIBS += $(shell ${R_HOME}/bin/Rscript -e "RcppParallel::RcppParallelLibs()")
However, R CMD check in R 3.5.0 generates a warning apparently because +=
and
.r-forge.r-project.org> on behalf of
> Yixuan Qiu <yixu...@gmail.com>
> *Date: *Monday, April 16, 2018 at 11:53 AM
> *To: *Murray Efford <murray.eff...@gmail.com>
> *Cc: *"rcpp-devel@lists.r-forge.r-project.org" <
> rcpp-devel@lists.r-forge.r-project.org>
;
> On 16 April 2018 at 13:41, Murray Efford wrote:
> | I read in the RcppParallel blurb "The code that you write within parallel
> | workers should not call the R or Rcpp API in any fashion", which is
> | admirably clear. However, it leaves me without threadsafe access to
&g
