similar to: Problem when building a test R package on PC

I am experiencing an OOLOCK error when attempting to update packages to my site-library. I have an identical setup on my local Linux machine, but this problem on the remote Linux machine (PPC cluster) started about 3 weeks ago and is present whether I used R-devel or R-2.6.0 or R-2.5.1. Also, of course I manually remove the 00LOCK folder after each failed attempt. Below is my error output,

Dear R-sig-debian, As of last night, we are running into a build failure when trying to compile the development version of R from the svn repository, Revision: 64090: ./configure && make -j4 distclean && ./configure && make -j4 [lots of normal compile output not shown...] building/updating vignettes for package 'utils' ... processing 'Sweave.Rnw' Error:

Dear R-Devel, Note: I posted a similar message to R-sig-debian yesterday because I assumed it was a Debian issue, received response that it it may be more appropriate for r-devel since it involves building from the svn version. As of Oct 21, we are running into a build failure when trying to compile the development version of R from the svn repository. The problem still persists as of

Hi, since a couple of days ago I see failures when using R CMD INSTALL -l lib path-to-src/pkg.tar.gz This occurs in automated library updating via a shell script and is caused by the immediate preceding call to leave an 00LOCK folder even though the package installation of that call succeeded. This occurs at random (no obvious/systematic correlation to package name or or such) and only for

Hi, On a new pc, I am trying to 'CHECK' an R package containing only R code but the process is hanging and I cant see why. The 00check.log file shows * using log directory 'c:/temp/opRisk.Rcheck' * using R version 2.2.1, 2005-12-20 * checking for file 'opRisk/DESCRIPTION' ... OK * this is package 'opRisk' version '0.2' * checking if this is a source

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

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

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 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:

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 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’

Hello, There seems to be a minor conflict of interesting in R CMD check. It creates a log directory, then gives a WARNING about it being there: * using log directory /home/darstr/Repitools_github/pkg/Repitools.Rcheck * using R version 2.13.0 RC (2011-04-05 r55310) * using platform: x86_64-unknown-linux-gnu (64-bit) * using session charset: UTF-8 ... ... * checking

Dear all, I am trying to build a home-made package (log2html) to log R output to an HTML file. The package can be build successfully under Solaris, however I am unable to build the system under Windows 2000 Professional. I read (and tried to follow to the letter) Duncan Murdoch's "Building R for Windows" (http://www.murdoch-sutherland.com/Rtools/), in combination with the newest

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.

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

Hi, all, I just recently upgraded my computer though I'm using the same OS (XP). But now I'm having difficulty building packages and I cannot seem to solve the problem. I'm using R-2.1.1pat on Windows XP. Here is what I tried: D:\Users\sundard\slib\sundar\R>R CMD CHECK sundar * checking for working latex ... OK * using log directory

Hello, I have a package with a namespace. Because I use Roxygen that overwrites the NAMESPACE file each time it is run, I use a R/zzz.R file with an .onLoad() and .onUnload() functions to take care of loading and unloading my shared library. The problem: if I load my library from a local directory, then the unloading of the package fails, e.g: # loads fine >library(Foo,

Hi: I have have taken over from a colleague who prepared an R package and failed to build it on Windows. I am doing this with unix as I am a mac user. Below is the output I get when I use the build command: [gattuso:unix/R/CO2.Rcheck] gattuso% R CMD build CO2 * checking for file 'CO2/DESCRIPTION' ... OK * preparing 'CO2': * checking whether 'INDEX' is up-to-date ...

Hi, This is a follow up to: https://stat.ethz.ch/pipermail/r-devel/2010-July/057921.html The Bioconductor daily builds have been reporting a lot of strange things lately on Windows using R-2.12. This started 2 or 3 months ago and things are not getting better with recent R-2.12. Here is a sample from today's build results. We use Windows Server 2003 R2 for the 32-bit builds, Windows