similar to: R CMD check and directory/package name

I have a samll package that works well and complies nicly on WinXP, using R-2.4.1 Now I want to add a document so i make a folder inst\doc and put the .tex and .pdf in there. But the complation then crashes. Is this because the installin expects some file to be present in inst if an inst folder is there? This is how the thing progress is on my command promp:

Hello, I am having an issue with R CMD check with the nightly build of RC 2.3.0 (listed in the subject.) The problem is this warning: * checking if this is a source package ... WARNING Subdirectory 'src' contains: README _Makefile These are unlikely file names for src files. In fact, they are not source files, but I do not see any reason why they cannot be there, or why I need to

Dear DevelopeRs, the issue I am stuck with (I am on Windows, R-2.11): My Miktex (version 2.8) does not work with R CMD check, although Miktex on its own can pdflatex the tex-file in the Rcheck directory. (This issue has been going on for a while, and now, after having updated to R-2.11, I finally want to get it fixed.) Although I have found several similar posts, none of the answers appears

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

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

Dear List, I have a problem building an R package using R 1.7.1 that I cannot resolve myself. R CMD check tells me that functions I documented properly in Rd-files are not documented and gives a TeX error at the end, altough the Rd files check is OK. I have three fucntions, one gets through without complaining, the other two don't. All the docu for the example data is also OK. I went through

Hi everyone, I am trying to build a R library called nnNorm but I have some troubles checking and installing it. Here is the setup: If I don't use a inst\doc directory(with the vignettes files) in my source, the install step is working fine: C:\test>RCMD INSTALL nnNorm ---------- Making package nnNorm ------------ adding build stamp to DESCRIPTION installing R files installing

Dear R developers, When building/checking my package (in R 2.6.1 under windows) I run into some messages that I do not completely understand and that do not give me precise enough leads to pinpoint where the error in my package is. I would be very grateful for any suggestions. Did anyone else encounter the same problem before? When building or installing the package, I get the message (no error

Hi I am still trying to wrap up a package using Rcmd (in windows 2000 professional with R 1.8.1). I have made some progress - and now at least Rcmd check works - it still giving me an error message when it creates latex help files though. Thus I get: c:\rpack> Rcmd check test * checking for working latex ... OK * using log directory 'C:/rpacks/test.Rcheck' * checking for file

Hello! I am building a package, which includes also one Fortran subroutine, which works fine if I compile it as a shared library and load it into R via dyn.load(). However, when I launch R CMD check it doesn't stop with checking examples. It's just doing and doing ... I pasted the whole output from R CMD check. Does anyone have any suggestions? I'm still using R 2.0.1.

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

Hello, I have a problem with the checking and building of R packages that contain C or FORTRAN code. I have implemented R 2.3.1 (2006-06-01) and the corresponding toolset under Windows XP and Windows 2000. The MinGW compiler components are (exactly as recommended for R 2.3.1) gcc-core-3.4.5-20051220-1.tar.gz gcc-g++-3.4.5-20051220-1.tar.gz gcc-g77-3.4.5-20051220-1.tar.gz

Dear all: I ?m a newer. I have some problem when I check my package. The error messages were as follows. It shows that the problem is about Rd file. How can I find where the error is? How can I do?? c:\temp>Rcmd check bear * checking for working pdflatex ... OK * using log directory 'c:/temp/bear.Rcheck' * using R version 2.7.0 (2008-04-22) * using session charset: CP950 *

Hi, For the first time I have a strange behaviour when checking a package before 'packaging' the code. Looks like a file cannot be read. rcmd check pgirmess * using log directory 'U:/Documents and Settings/pgiraudo/Mes documents/R/pgir_arch/pgirmess_arch/On work/pgirmess.Rcheck' * using R version 2.13.2 (2011-09-30) * using platform: i386-pc-mingw32 (32-bit) * using session

Hi, I have just updated R from version 2.8.1 to version 2.9.1. I am running Windows XP Professional, Service Pack 3. With the update, I decided to update a set of packages that I maintain by compiling them for the new version. Everything worked fine except for one package. This package is unique (among the six I was working on) in that is stored on a UNIX-based file server that is

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'

In version 2.8.1, running Rcmd check on the package foo would leave the file foo-manual.tex in the folder foo.Rcheck. But as of 2.9.0 only foo-manual.pdf and foo-manual.log are there. Is this intentional? Anyway it is inconvenient, because I would occasionally like to include the manual at the end of a set of exercises, and this was a convenient file to \input with a few select %'s added.

I have noted that the later versions of Rcmd check cleans out the directory pkg.Rcheck so that only package-manual.log and package-manual.pdf are left. Formerly the package-manual.tex was around too --- very handy for various purposes. Is there a way to generate the .tex - version of the manual for a package? br. Bendix ______________________________________________ Bendix Carstensen Senior

Hi I have a package that I'm testing. It seems to install fine and it works, as far as I can tell. For example, I can install the package, and use it, and source the test suite with no errors. My problem is with R CMD check. It passes on R-2.2-0: Robin-Hankins-Computer:~/scratch% R CMD check ./partitions_1.1-0.tar.gz * checking for working latex ... OK [snip] make[1]: Leaving directory

Hello! I have some problems using Rcmd, bacause I get errors I do not understand. I will write down what I did. Perhaps you can help me? I have a small would-be package called "globaltest", containing only the files DESCRIPTION INDEX R/globaltest.R man/globaltest.Rd I say: C:\>Rcmd check C:/Goeman/globaltest In the output it first complains that 'sh', 'make',