similar to: R CMD CHECK doens't run configure when testing install? (Revised)

Function/file names are hypothetical. Say I have written myfunction.R, which calls myfunction.c via .C("myfunction", ...). I've compiled successfully myfunction.c via R CMD SHLIB myfunction.c in the terminal. Then, in the R console: dyn.load("myfunction.so") source("myfunction.R") test <- myfunction() # works fine So everything is in order, myfunction works

Dear friends, I am building an R package called *mypackage*. I followed every possible steps (to my understanding) for the same. I got following problem while doing *R CMD check mypackage*. * installing *source* package 'mypackage' ... ** libs cygwin warning: MS-DOS style path detected: C:/PROGRA~1/R/R-213~1.0/etc/i386/Makeconf Preferred POSIX equivalent is:

I too have this problem. Everything worked fine last year, but after updating R and packages I can no longer do word stemming. Unfortunately, I didn't save the old binaries, otherwise I would just revert back. Hoping someone finds a solution for R on Windows. Thanks! There is a potential solution for R on Mac OS from Kurt Hornik copied below, but I cannot get this to work on Windows.

Dear all, I have some troubles using the stemming algorithm provided by the tm (text mining) + Snowball packages. Here is my config: MacOS 10.5 R 2.12.0 / R 2.13.1 / R 2.14.1 (I have tried several versions) I have installed all the needed packages (tm, rJava, rWeka, Snowball) + dependencies. I have desactivated AWT (like written in

Folks: sessionInfo() R version 2.15.0 (2012-03-30) Platform: i386-pc-mingw32/i386 (32-bit) locale: [1] LC_COLLATE=English_United States.1252 [2] LC_CTYPE=English_United States.1252 [3] LC_MONETARY=English_United States.1252 [4] LC_NUMERIC=C [5] LC_TIME=English_United States.1252 attached base packages: [1] datasets splines grid tcltk stats graphics grDevices [8] utils

Folks: sessionInfo() R version 2.15.0 (2012-03-30) Platform: i386-pc-mingw32/i386 (32-bit) locale: [1] LC_COLLATE=English_United States.1252 [2] LC_CTYPE=English_United States.1252 [3] LC_MONETARY=English_United States.1252 [4] LC_NUMERIC=C [5] LC_TIME=English_United States.1252 attached base packages: [1] datasets splines grid tcltk stats graphics grDevices [8] utils

The help page for INSTALL says, in part, Some package sources contain a `configure' script that can be passed arguments or variables via the option `--configure-args' and `--configure-vars', respectively, if necessary. The latter is useful in particular if libraries or header files needed for the package are in non-system directories. In this case, one can

Hi all, R CMD check does not work for me under Windows. This is the error R CMD check mypackage.tar.gz * checking for working latex ... OK tar: and: Not found in archive tar: Settings/miguez/ ... /00_pkg_src: Not found in archive tar: Error exit delayed from previous errors Error: cannot untar mypackage.tar.gz I know tar is available because R CMD build created the tarball in the first place

Hello, All: How can I obtain the location of an example data file in a package during "R CMD check"? I want to include sample raw data files in a package and have them read by a function in the package. It occurs to me to put such a file in "\inst\rawdata" and have examples find the data using something like "system.file('rawdata',

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

Hi I have a package which was built using R 1.9.1 and everything worked fine. I recently upgraded to R 2.0.1 and tried to re-install my package - and I got: Error in library(mypackage) : 'mypackage' is not a valid package -- installed < 2.0.0? So I tried rebuilding it using my new version of R: R CMD BUILD --binary mypackage hhc: not found cp: cannot stat `mypackage.chm': No

I'm putting together an R package. I would like to show example code in the vignette, where example data files (included in the package) are used to generate an (example) output file. I read about using example data in Hadley Wickham's post ( http://r-pkgs.had.co.nz/data.html), and believe I should keep my example data as raw data, as it must be parsed to generate the output. So, I

When I run the following: cd \Rpkgs rcmd install mypackage -l library I get a message that it cannot find quadprog which is a library that mypackage depends on. Error: package 'quadprog' could not be loaded I previously used C:\Program Files\R\rw2011\library as my library for CRAN packages and did not have a problem but now that I use C:\Program Files\R\library this problem

Dear All, I have seen a number of e mails on this topic but I have not seen a general solution to date. I have Fortran and C source codes and they have been compiled successfully using: R CMD build mypackage And R CMD install mypackage Without error messages. I then open R and tests out two functions and get: > pgl(0.2,1,2,3,4) Error in

Dear All, I have seen a number of e mails on this topic but I have not seen a general solution to date. I have Fortran and C source codes and they have been compiled successfully using: R CMD build mypackage And R CMD install mypackage Without error messages. I then open R and tests out two functions and get: > pgl(0.2,1,2,3,4) Error in

I have some questions about 1. nomenclature, 2. recommended file locations and 3. overall procedure related to creating packages. To the extent that it matters, examples here relate to Windows XP R 2.0.1 beta. The questions are interspersed and prefaced with ***. My understanding is that there are actually 6 forms of a package that one should use in package development: 1.

I have question regarding package installation. What is the difference between check, INSTALL, build and build --binary, which imply which and what order does one normally perform them? I have been trying: R CMD build /mypackage R CMD check /mypackage R CMD build --binary /mypackage in that order but wanted to check that this is right. Also, what portion of the check process can be run

Hi All, Apologies in advance if this is not the right email to post this question. I successfully created my first R package myPackage1. Now I want to create another R package myPackage2 which requires functions from myPackage1. However when I try R CMD check myPackage2 I get the following error * checking for working pdflatex ... OK * using log directory

Dear R-users, I am having some issues with a package I am working on (using R 2.12.1 in a Linux environment) and would like to have your opinions/advises. My package - let's call it mypackage for the purpose of this email - passes all checks of R CMD check, except for the following failure message: Error : .onLoad failed in loadNamespace() for 'mypackage', details: call:

Hi I found yum-downloadonly and executed my command do that and save the dependencies in my current directory. Now when I execute my command: rpm -i mypackage all the dependencies are not found even though they are in the current directory. if I do a "yum install mypackage" (and its in the current directory) its not found either. How do I now install the mypackage in the current