similar to: problem with rcmd build R-devel

Hola! I got past the problems I asked about two days ago, thanks. No I am updating CRAN package asypow (the daily package check on CRAN gave warnings due to .Rd problems, fixed). Now it PASSED Rcmd check (WindowsXP home edition, rw2000dev, on a new toshiba laptop, if that matters.) but then Rcmd build --binary gives problems: . . . preparing package asypow for lazy loading Error in

hello, i try to create a package , and i call a library in the namespace file such as : useDynLib(quadprog) after checking my directory with the command "rcmd check" (i am on WindowsXP) i get an error: package / namespace load failed the path of the library is: D:\R\library\quadprog the path of the building files is: D:\RBuild\svcR and the comand i use to compile is: rcmd

Dear R community, I am running R 2.0.1 on a Windoze XP OS. I recently upgraded from R 1.9x to 2.0.1 and I am currently upgrading a my personal function packages. My other packages compiled without a hitch but I am having a difficult time with my largest package. Can someone please help me with the following error message "Error in parse(file, n, text, prompt) : syntax error on line

I'm using R 1.4.1 under Windows 2000 and am experiencing difficulty installing a package. I've included an example output using Rcmd build, but the same problem occurs with Rcmd check and Rcmd INSTALL. The error (make[1]: /bin/sh.exe: Command not found) is not a new one - it's referenced in readme.packages among other locations. I've placed a copy of sh.exe in C:\bin, but it

Has anyone had success building a package on a windows machine? I am trying the following command with no luck (perhaps my flags are incorrect?). At this point I am stuck. Any help greatly appreciated. Niels Waller (BTW - I have no idea why it cannot find sh.exe since I have it is a directory that is specified in a path statement) H:\R\bin>rcmd build --binary --use-zip h:\taxon2 * checking

Dear all I am trying to build a package in Windows. I use the following command (which it used to work with previous versions ) and I am getting the following error #-------------------------------------------------------------------------------------------------------------- C:\PROGRA~1\R\rw2000\bin>Rcmd build --binary --use-zip C:\PROGRA~1\R\rw2000\src\library\gamlss * checking for

I just installed the R-patched 1.4.0 and for some reason I now have trouble compiling R packages - I could compile it a few weeks ago with R 1.4.0 released in December. This only happens if I put the --binary option in. For example: Rcmd build --binary cw returns the error: make: Entering directory `/cygdrive/c/PROGRA~1/R/RW1040/src/gnuwin32' make DLLNM= \ -C C:/MyRWork/cw PKG=cw

I get the following error when building R from the subversion server as well as the latest tarball. I am on Windows XP, and I recently updated my MinGW installation. It's quite possible I am doing something wrong, but I am not sure what that might be. making console.d from console.c making dataentry.d from dataentry.c making dynload.d from dynload.c making edit.d from edit.c making editor.d

I am trying to build a R 1.7 package under Windows NT. I created the DESCRIPTION file, the RD file and added the code to the R folder. I also downloaded and installed the Rtools package and have Perl 5.0. I know that Perl, Miktex, and gcc are working. I also have my PATH variable set correctly. I can fake install my package by removing the *.R from the code file, using Rcmd Rdconv to create

Hi all, Most of the analyses I do are short little once-and-done type things that are easily encapsulated in a .Rnw file. However, I sometimes end up with projects that take an extended amount of time. Usually these projects are not easily encapsulated in an .Rnw file, so I have been using a single .R file with lots of comments. The problem with this approach is keeping track of what you have

Hello, I am trying to build an R package for Windows from an R package for Linux. There seems to be a "windres" problem somewhere. Here's what I get. C:\Temp>Rcmd build --binary VGAM > mm make[2]: windres: Command not found make[2]: *** [VGAM_res.o] Error 127 make[1]: *** [src/VGAM.dll] Error 2 make: *** [pkg-VGAM] Error 2 In more details, it goes like the following.

I want to share this knowledge to save you the hours it took me to troubleshoot the following problem. Maybe you already know about this, but I certainly didn't. In the end I also suggest an update fix. PROBLEM: I have been building packages for a couple of months now without any problems. However, a couple of hours ago I ran into a strange problem, which I first couldn't understand or

On Solaris when my package is built, I get the following result: creating vignettes ...Segmentation Fault - core dumped OK My question isn't why I get a segfault, but why does build return an OK after such an inauspicious event? Is build only supposed to error out if something more central to the package is off? R CMD check does issue a warning that the vignette is missing, so maybe that

> R.version.string [1] "R version 2.1.0, 2005-03-17" I don't see anything in either https://svn.r-project.org/R/trunk/NEWS or in the Changes file for R-2.1.0 about changes in package.skeleton() (nor in the help page), but when I run this function, all the .Rd files produced are of the data format even if all I have in my .GlobalEnv are functions. A trivial example is to run the

I just built R-devel from source on OS X (Tiger), using the subversion sources. Running ./tools/rsync-recommended didn't download rcompgen. I checked http://cran.r-project/src/contrib/2.7.0/Recommended and indeed, this package is not there. If I try to install using install.packages I get > install.packages("rcompgen", type="source") --- Please select a CRAN

The function knn.cv in the class package doesn't have error checking to ensure that the length of the classlabel argument is equal to the number of rows in the test set. If the classlabel is short, the result is often a segfault. > library(class) > dat <- matrix(rnorm(1000), nrow=10) > cl <- c(rep(1,5), rep(2,5)) > cl2 <- c(rep(1,5), rep(2,4)) > knn.cv(dat, cl) [1] 2

On Thu Jan 9 2014 03:47 Henrik Bengtsson wrote: > This is is an issue that bugged me for a while. I encountered a year > ago (April 2012) when I first tried to build R from source on Windows. > I never figured out what the solution is or if I'm doing something > wrong myself (but I have found a tedious workaround). I'm still on > the same Windows 7 Ultimate machine with

If one wants to unload compiled code for a package containing a namespace, my understanding is that .onUnload() should be used, with a call to library.dynam.unload(). This is used in e.g., the stats and methods packages, but it appears to me that the compiled code is not being unloaded when the package is detached(). Am I misunderstanding something? Best, Jim > search() [1]

A command R CMD build <pkg> that fails, e.g., because of C code compilation errors, leaves a directory %TMPDIR%/Rinst.xxx containing the file R.css. Although R CMD INSTALL --build cleans up after itself, build does not. A fix is below. Also, build.in references Rcmd.exe, which I thought was no longer necessary? Index: build.in

Hi, all. I was trying to build my R package with R 2.15.1 32bit and win7. I basically follow the routine in Steven Mosher's blog http://stevemosher.wordpress.com/step-10-build/ After I fixed the path, and built the skeleton of the package, I started command prompt and used the following commands in building my package Rcmd check myPackageName Rcmd build myPackageName Rcmd check