similar to: Solved two problems with Cygwin

I noticed that in "R version 2.4.0 alpha (2006-09-16 r39365)" on Windows XP that I get this error: C:\Rpkgs>Rcmd install mypkg no Perl script 'install' The same command worked with no error in 2.3.1pat. If I capitalize INSTALL it does work; however, this was not necessary previously. Note that C:\Rpkgs>Rcmd check mypkg unlike install, still works in either lower or

dear R user, I al rying to compile an R package with some C code. everithing work fine as long as I work in Linux or MaCOX. unluckyly I can cant compile it under Windows, here is the error, but I cant figure it out what is the problem. can you help me? * using log directory 'C://MyPKG.Rcheck' * using ARGUMENT ' ' __ignored__ R version 2.11.0 (2010-04-22) * using session ARGUMENT

In performing Rcmd check I am getting this output regarding using Argument '' and a NULL package not found and it stops with an error: * using log directory 'C:/Rpkgs/sqldf.Rcheck' * using ARGUMENT ' ' __ignored__ R version 2.5.1 (2007-06-27) * checking for file 'sqldf/DESCRIPTION' ... OK * this is package 'sqldf' version '0.1-0' * checking package

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 encountered and apparently overcame problems following Yan and Rossini?s procedure for "Building Microsoft Windows Versions of R and R packages under Intel Linux" (http://cran.r-project.org/doc/contrib/cross-build.pdf): I have successfully cross-compiled R packages for Windows on a FreeBSD 4.10 i386 system. My revisions to Makefile-rcb (http://cran.r-

My setup: Windows XP, R-2.6.0, Cygwin (not the Rtools version) When I tried to build a package, I was given this message: tar: c\:/X/Rpkgs/Drydown_1.41.tar: Cannot open: Input/Output error Even manually typing the following caused the same error: tar chf 'c:/X/Rpkgs/Drydown_1.41.tar' Drydown I looked at the 2.5.1 and 2.6.0 build scripts. After restoring this section to the 2.6.0 build

I'm sorry but that is not a working example. A working example needs to create the plots being used. For example, stealing some code from https://rpkgs.datanovia.com/ggpubr/reference/ggarrange.html #================================================================= data <https://rdrr.io/r/utils/data.html>("ToothGrowth")df <- ToothGrowthdf$dose <- as.factor

Full_Name: David O. Nelson Version: 1.4.1 OS: solaris 2.7 Submission from: (NULL) (128.115.150.74) Putting patterns in .Rbuildignore has no effect when the tar being used is gnu tar (1.13) on solaris 2.7, whilst /usr/sbin/tar works perfectly. TO REPRODUCE: The current directory contains a source package directory ./mypkg... bimini.jgi-psf.org% echo >mypkg/foo bimini.jgi-psf.org% echo

Hi, my name is Paula. Im trying to learn how to build an R package in Windows XP using a simple example which includes a C source code. The foo.c file is located in mypkg/src/foo.c. I used the command Rcmd build --force --binary [pkgpath]. The problem is when I install the zip file in R the function foo doesn?t exist. The result a recieved during the building process is copied below. I really

Hi R Gurus! I'm trying to create a test package using the package.skeleton function. I wanted to add some compiled code too. In the src library, I put together a baby subroutine, compiled it and created a test.dll When I use the R cmd build, it works fine. But I get into trouble with the R CMD check section. /home/Desktop/R-2.5.1/bin # ./R CMD check mypkg * checking for working latex ...

Hello useRs I am trying to build a package for personal use and for making easier working with other people but I keep getting the same error message about the DESCRIPTION file not existing. when trying to install from a source tar.gz file: Error in .read_description(dfile) : file 'C:/Users/Propriétaire/AppData/Local/Temp/RtmpHFMONb/R.INSTALL647a3535/mypkg/DESCRIPTION' does not

Hi: I'm trying to create a package to pass to someone else to use a group of functions with help files. I'm working on Windows XP. Step One: I use the example > ## two functions and two "data sets" : > f <- function(x,y) x+y > g <- function(x,y) x-y > d <- data.frame(a=1, b=2) > e <- rnorm(1000) > >

I'm having a very hard time making R CMD check produce a clean check on examples because of the timings inserted into examples by R CMD check. I am getting a difference on every example output caused by timing information being inserted by 'R CMD check'. The current 'Writing R Extensions' manual[1] states on p. 14: If directory tests has a subdirectory Examples

Jun hi again! Sorry for bothering. Although I had no problem with building Windows package under Linux, I noticed that man pages are not processed as they should or maybe I have a problem with my setup. My package is called 'GeneticsPed'. Instead of HTML or text files I just got a GeneticsPed.Rd.gz in man directory of a package (this is within GeneticsPed_0.1.zip file!). The file

Dear list, I've a package, myPkg, which was developed on R v 2.6.1. I have installed R v2.9.2 from source, with a shared library and tcktk support. The package, myPkg, depends on RSPerl, and imports it in its NAMESPACE. I've downloaded and installed RSPerl using command: >R CMD INSTALL -c --configure-args="--with-modules='IO \ Fcntl Socket Storable XML::Parser::Expat

Hi, 'R CMD INSTALL mypkg' and 'install.packages(mypkg, repos=NULL)' don't update mypkg help pages when mypkg is a source directory. They only install new help pages if there are some but they leave the already installed pages untouched. So you end up with mixed man pages from different versions of the package :-/ I found no mention of this in 'R CMD INSTALL --help' or

I would like to be able to load two versions of a package at once and to do that was thinking of giving each version a different package name in the DESCRIPTION file and the building and installing each such version separately. library(myPkg1) library(myPkg2) and then use myPkg1::myFun() and myPkg2::myFun(). To do that easily it would be convenient if one could change the package name in only

Dear friends, I am writing a package that I think may be of interest to many people so I am in the process to build-check-write-thedocumentation for it. I have some questions regarding the "rules" that a package should abide in order to be consistent with the other packages on CRAN. I have read and reread the Writing R extension manual and googled the mailing list and I have found

I am building a package say mypkg. Five months ago, when I built the package I got the mypkg manual in pdf format. Today, after making updates, I build the same package, same name, and steps; unfortunately I do not get the manual in pdf format. Rather I get the following message: cd: can't cd to /cygdrive/c/Documents saving output to 'mypkg-manual.pdf' ...Done Could any one

----- Forwarded by Ajay DAS/US/BMNA01 on 05/19/2008 03:11 PM ----- Ajay DAS To: r-help