Skip to content
Prev 59138 / 398502 Next

problems with compiling a package

On Tue, 16 Nov 2004 r.ghezzo at staff.mcgill.ca wrote:

            
What exactly is `R2.0.0 patch'?  If you mean 2.0.0 patched, it has a date, 
and the date is crucial.
My guess is that this comes from tools:::.split_description which has

     if(!is.na(Built <- db["Built"])) {
         Built <- as.list(strsplit(Built, "; ")[[1]])
         names(Built) <- c("R", "Platform", "Date", "OStype")
         Built[["R"]] <- package_version(sub("^R ([0-9.]+)", "\\1",
                                             Built[["R"]]))
     } else Built <- NULL

so probably your DESCRIPTION file is faulty.  Did you have a Built: line
in it that you put there yourself?  I can reproduce this by doing so.
If so, `Writing R Extensions' does say

   There should be no @samp{Built} or @samp{Packaged} fields, as these are
   added by the package management tools.

and R CMD check on such package throws an immediate error.
Please do read the NEWS (or ONEWS) file!  It says in the first 20 lines

         Packages are by default installed using lazy loading if they
         have more than 25Kb of R code and did not use a saved image.