[Rd] Export tools:::analyze_license()?

package. Will Landau [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

[Rd] FW: CRAN check errors: drake 4.1.0 on r-devel-linux-x86_64-debian-clang

quot;Should also be found.") digest("Should NOT be found.") } print(find_namespaced_functions(f)) # Expected output: # [1] "digest::digest" "digest:::digest" From: Will Landau Sent: Saturday, September 16, 2017 11:16 PM To: 'Gábor Csárdi' ; 

[Rd] R-devel r73293 and the testthat package

Hello, Windows R-devel no longer lets me use testthat even though the CRAN checks are pretty much clean. I have copied my session output below. Will R Under development (unstable) (2017-09-16 r73293) -- "Unsuffered Consequences" Copyright (C) 2017 The R Foundation for Statistical Computing P

Re: [Rd] cuda-memcheck to debug CUDA-enabled R packages

Counter-edit: it turns out that that kind of hack doesn't work. See this post . -- View this message in context: http://r.789695.n4.nabble.com/cuda-memcheck-to-debug-CUDA-enabled-R-packag

[Rd] Note: information on .o files is not available

mentation, or in the source of the devtools package. Here is the full output of my R CMD check. * using log directory ‘/home/landau/heterosis.Rcheck’ * using R version 3.1.0 (2014-04-10) * using platform: x86_64-unknown-linux-gnu (64-bit) * using session charset: UTF-8 * checking for file ‘h

Re: [Rd] cuda-memcheck to debug CUDA-enabled R packages

Edit: I solved this problem by putting R CMD BATCH --no-save < test.R into a script (say, run.sh), and then running $ cuda-memcheck ./run.sh -- View this message in context: http://r.789695.n4.nabble.com/cuda-memcheck-to-debug-CUDA-enabled-R-packages-tp4691668p4691766.html Sent from th

Re: [Rd] debugging a CUDA-enabled R package with cuda-memcheck

Edit: I solved this problem by putting R CMD BATCH --no-save < test.R into a script (say, run.sh), and then running $ cuda-memcheck ./run.sh -- View this message in context: http://r.789695.n4.nabble.com/debugging-a-CUDA-enabled-R-package-with-cuda-memcheck-tp4691669p4691765.html Sen

[Rd] cuda-memcheck to debug CUDA-enabled R packages

I'm building a simple R extension around a CUDA-enabled dynamic library, and I want to run the whole package with cuda-memcheck for debugging purposes. I can run it just fine with Valgrind: $ R --no-save -d valgrind < test.R However, if I try the same thing with cuda-memcheck, $ R --no-save -d c