similar to: 1.2 R CMD check

I am not sure if this is already known. I checked BUGS and found some references to similar behavior when R_HOME is set? Here is what I get: (1) Fresh build of 1.4.1 under Linux/RH-7.2. All tests pass. > R CMD check ctest * checking for working latex ... OK * using log directory `/home/andyj/stat/R-1.4.1/library/ctest.Rcheck' Installing *source* package `ctest'

I am trying to re-organizing my Makefile for testing my R packages and I am having trouble finding a structure I like. The problem seems to be that "R CMD check", which does wonderful things, does not allow dependency information to flow through very gracefully. That is, since everything is copied into the pkg.Rcheck directory, it is difficult to make any changes to source files without

Hi! My Platform: Windows 2000 R version >1.5 Active Perl 5.6 Rtools at the start of the PATH. I am trying to build a package. The functions are written only in R (no C code). I am trying to proceed as described in R-exts.pdf But instead to get a build package i am getting (see below). At first glance it seems to me that i understand the output. At something similar i am looking most of my

Dear R-devs, Scenario: When checking a package via `R CMD check package_tar.ball`, required / suggested packages may be missing. R subsequently returns a list of packages that are missing (delimited by spaces). Example: ``` R CMD check glmSparseNet_0.99.13.tar.gz * using log directory '/home/ubuntu/Bioconductor/glmSparseNet.Rcheck' * using R Under development (unstable) (2018-06-06

Hi, there, I used R CMD check to build my "ATGGS" package under window XP system. My R version is 2.7.2. But I encounter some problems. The log file is like: ********************************************************************************** installing R.css in C:/ATGGS.Rcheck ---------- Making package ATGGS ------------ adding build stamp to DESCRIPTION installing R files

Hi, there, I used R CMD check to build my "ATGGS" package under window XP system. My R version is 2.7.2. But I encounter some problems. The log file is like: ********************************************************************************** installing R.css in C:/ATGGS.Rcheck ---------- Making package ATGGS ------------ adding build stamp to DESCRIPTION installing R files

To whom it may concerned, I'm trying to build a new R package in a windows platform. Before that, I tried to check the previous well-know package from the CRAN using the Rcmd command. But I got the error messages as below. I think this comes from the parsing error from the Perl script in $RHOME/bin/check. In the following example, 'Program Files' is splited into 'Program',

Dear R devel I am experiencing a problem using R CMD check. I tried to specify the argument outdir, but get every time the error message: Warning: unknown option ‘--outdir==RCHECK’ This happens both on R 2.15.2 Linux, as well as R 3.0.1 Windows, with latest Rtools. Is it just that I am not passing the argument the right way, or is there an issue with R CMD check? I tried to write the argument

Using R 1.7.0 I get * checking parcv-manual.tex ... ERROR Could not create DVI version. Although there is no apparent error. The dvi file exists. Possibly there is some problem with my TeX setup, but the following messages don't suggest that either. Here's the full log, which does show some documentation issues: sheep:~$R CMD check --library=.R/library/ src/parcv * checking for working

In revising the splancs package, I use R CMD check. After a number of changes to various files in the directory tree, R CMD check fails at the * checking for undocumented objects ... ERROR stage as shown below. But running undoc() in R (pointed at the Rcheck directory, not on the older version) doesn't show the same error, and grep on the Rcheck R code finds the function. I ran undoc() under

I am trying to figure out why checking my package is deleting my inst/doc/ directory when I do it in RStudio. Along the way I've hit another puzzle. In RStudio the check runs and is mostly OK, aside from the deletion. But when I try with vanilla R, the check fails almost immediately: -------------------------powershell--------------------------- PS C:\Users\rdboylan\Documents\BP\pimex>

? Fri, 3 May 2024 19:45:08 +0000 "Boylan, Ross via R-help" <r-help at r-project.org> ?????: > & $R CMD check . > * checking for file './DESCRIPTION' ... ERROR > Required fields missing or empty: > 'Author' 'Maintainer' You're checking a source package directory. This could work, but it's much easier and more reliable to (1) build

Dear r-devel members, I tried to build R packages on a PC running Windows XP but experience problems. However, it is ok when there is no inst directory in a package. Any help would be appreciated. The following is an example, C:\work>R CMD check VR_7.2-19.tar.gz * checking for working latex ... OK * using log directory 'C:/work/VR.Rcheck' * using R version 2.1.1, 2005-06-20 *

Hi! All. I want to make R package with "http://code.google.com/p/uchardet/" library. But I encountered error. Executable file with -lchardet works well but shared library didn't work with dyn.load() with Rcpp. Can any one give some tips? * installing *source* package ‘Ruchardet’ .. ** libs g++ -I/usr/share/R/include -DNDEBUG -I/usr/local/include -I/usr/include

Hi [MacOsX 10.4.6; R-2.2.1] I have a bundle that comprises three packages. I want to run R CMD check on each one individually, as it takes a long time to run on all three. I am having problems. The bundle as a whole passes R CMD check, but fails when I cd to the bundle directory and run R CMD check on a package directory. The whole bundle passes: octopus:~/scratch% R CMD check

Hi, I have a couple of new errors in our package when I check it on R 2.13-rc (r55310). The first one that's mystifying me is * checking R code for possible problems ... NOTE Error : object normalizePath is not exported by 'namespace:utils' Error : object normalizePath is not exported by 'namespace:utils' Firstly, it's strange to see NOTE and Error being used

Dear R-users, I am going through the last steps of package prep before submission to CRAN and I have the following problem. My package contains a single vignette written in optimbase.Rnw and that in stored in /inst/doc. optimbase.Rnw contains multiple \input{} statements that refer to .tex files stored in /inst/latex.ref/, e.g.: \input{../latex.ref/optimbase-package.tex} When I compile my Rnw

Hi, I believe this is kind of a long standing bug though. In R-3.0.1, but this also happened in previous versions, the long version '--outdir' is not recognised: For `R CMD check --outdir=mydir pkg_0.1.tar.gz` we get: Warning: unknown option ‘--outdir=mydir’ But with `R CMD check -o mydir pkg_0.1.tar.gz` we get: * using log directory ‘/home/renaud/Documents/projects/mydir/pkg.Rcheck’

Dear all, I'm puzzled by the error I get from R CMD check one of my packages. I'm running R CMD check with the --as-cran flag and it get the error both from running it from the command line as from within Rstudio. On the same machine R CMD check on my GRTS package (https://r-forge.r-project.org/R/?group_id=1027) works fine. Any suggestions on how to fix this? I can send the source code

Hi, All: What might cause "R CMD check" to report, "could not find function" for a function that has long been in the 'fda' package? Both Jim Ramsay in Ottawa, Canada, and I in San Jose, CA, get this same error. I replicated it with a fresh, anonymous checkout from R-Forge (svn checkout svn://svn.r-forge.r-project.org/svnroot/fda). With this, I did