similar to: modification time warning with R CMD check

It turns out that my web host doesn't allow direct links. Try going to http://www.warnes.net/downloads or getting it from the sourceforge snippet library https://sourceforge.net/snippet/detail.php?type=snippet&id=101149. -Greg > -----Original Message----- > From: Warnes, Gregory R [mailto:gregory_r_warnes at groton.pfizer.com] > Sent: Monday, May 13, 2002 10:15 AM > To:

R CMD check fails when the Depends field in the DESCRIPTION file includes a single package with `.' in the name. * checking for file 'financials/DESCRIPTION' ... OK * checking package directory ... OK * checking DESCRIPTION Package field ... OK * checking DESCRIPTION Version field ... OK * checking DESCRIPTION License field ... OK * checking DESCRIPTION Description field ... OK *

I'm trying to get the this Fortran array bounds check to run on my code as my package has been rejected for failing this test. I read writing R extensions and it appears to run this test I should use a Makevars file with one of the following two flags depending on my compiler: FCFLAGS = -g -O2 -mtune=native -fbounds-check FFLAGS = -g -O2 -mtune=native -fbounds-check and store it in the src

The inconsistency is that you use $<- to set the column, then [[<- to change it. Had you tried to set the column by x[[1]] <- as.character(x[[1]]) you would have seen the problem immediately (it does not work as you would have intended). If you want to be sure to turn off conversion to factor, you need to set the column to class "AsIs". My belief is that will behave

Hi, I wonder about the reason for the following lines: $ diff ~/local/lib64/R/bin/build /usr/lib64/R/bin/build 40c40 < my $revision = ' $Rev: 46832 $ '; --- > my $revision = ' $Rev: 45803 $ '; 576,579d570 < if(-r "Makevars") { < $makefiles .= " -f Makevars"; < R_system("${R::Vars::MAKE}

Thanks to Brian Ripley for suggesting, to my previous post about a problem with merge, that I trace through merge.data.frame. I did so with my test case and all seemed to be well until I got to: if (all.x) for (i in seq(along = y)) is.na(y[[i]]) <- (lxy + 1):(lxy + nxx) I believe that this code sets observations in y (which has been expanded to be the

I have a package in which I would like to store a LaTeX .tex file. It is not documentation on any particular function, but is related to the package. In thought that I could just create a "doc" directory under the "inst" subdirectory and place it there. I thought that things in "inst" were just recursively copied when the package was installed. Alas, when I check the

Thanks to Henrik Bengtsson, Martin Maechler, Brian Ripley, Jeff Gentry and David Brahm for taking the time to answer my questions about INDEX files in R packages. My key take-aways were: 1) All of this will be changing a lot in R 1.7.0-to-be, so don't sweat the details. 2) Many people run R CMD build before they run R CMD check. I found this quite surprising. I did not realize that R

In previous versions of R (at least in 1.5.1, I think), my practice was not to include an INDEX file in the package. R CMD check did not complain and an INDEX was created for me when I use R CMD build. At least, this is how I remember it. I thought that this was a good way to behave since it ensured that my INDEX was automatically kept up to date by R, without me having to worry about what

Dear all, bigKRLS, which has been on CRAN for a couple of years, had to be pulled recently due to what seems to be a sanitizer issue stemming from its use of bigmemory. bigKRLS works fine (we?ve used it ourselves on many different platforms and have had over 15,000 downloads without an end user reporting difficulties because of this issue). Unfortunately, we have been unable to reproduce the

All, When I try and compile a shared library (on WinXP) I get the following error: E:\data\proj>R CMD SHLIB toy_dll.c Makevars:1: *** missing separator. Stop. Has someone else had this error and fixed it? This code compiles and works fine on Linux (fedora core 2). Everything was working fine under R1.8.1 but I've broken something when I upgraded to R1.9.1. So I am assuming

As cool and wonderful as the package checking tools for R are, I sometimes am stymied when trying to track down a problem. For example, I occasionally see error messages when running R CMD check like the following: [...] * checking Rd files ... OK * checking for undocumented objects ... ERROR * in parse(file, n, text, prompt) : syntax error on line 932 * in undoc(dir =

The help for options says: echo: logical. Only used in non-interactive mode, when it controls whether input is echoed. Command-line options `--quiet' and `--slave' set this initially to `FALSE'. I don't think that this is correct for me. Consider the following session: mica|junk> ls test.R mica|junk> cat test.R cat("Why was this command

Le 27/09/16 ? 13:31, Dirk Eddelbuettel a ?crit : > > On 27 September 2016 at 09:37, Eric Deveaud wrote: > | Hello, > | > | I'm tring to install a Rpackage that holds some C//C++ code > | > | as far as I understood the R library generic compilation mechanism, > | compilation of C//C++ sources is controled > | > | 1) at system level by the ocntentos

I am just trying to adjust one of my packages so the C code builds in Windows. This is code that has been around for a long time, and I'm am only a casual reader of C, so it has had the "if it is not broken don't touch it" approach for many years. The section 1.2.1 "Using Makevars" of "Writing R extensions" starts: "Sometimes writing your own

Hi I've built a dll using Fortran code and can call it by either R or Fortran. Calling by the former gives me the wrong answer and the later gives the correct answer. >From what I've read, it looks like I should use the subroutines DBLEPR, INTPR and REALPR to print to the R console rather than using Fortran standard I/O and that if I use the command R CMD SHLIB source.f that these

Hello, I'm tring to install a Rpackage that holds some C//C++ code as far as I understood the R library generic compilation mechanism, compilation of C//C++ sources is controled 1) at system level by the ocntentos RHOME/etc/Makeconf 2) at user level by the content of ~/.R/Makevars 3) at package level by the content of src/Makevars Problem I have is that src/Makevars is ignored see

I have been working on an R package that calls C code using .C(). I recently started including some functions from the GNU Scientific Library in my code. The code runs fine on my machine when not wrapped in the package. But I get the following error from "R CMD check" * checking whether the package can be loaded ... ERROR Loading required package: splancs Loading required package: sp

One other solution that's only a little crazy: you could have a R function within your package that generates the appropriate (portable) Makevars, and within the package `configure` script call that function. For example" R --vanilla --slave -e "source('R/makevars.R'); makevars()" And that 'makevars()' function could generate portable

On May 13, 2015, at 2:28 PM, Henrik Bengtsson <henrik.bengtsson at ucsf.edu> wrote: > While at it: 'Makevars' is an R invention (i.e. documentation of it > is only available through the R docs), correct? /Henrik > Well, it's just a Makefile fragment that gets included along with the rest of the Makefiles, so for all practical purposes it's just a Makefile which