similar to: Warning when building packages and update suggestion

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

Full_Name: Henrik Bengtsson Version: 1.5.1 OS: WinMe Submission from: (NULL) (217.210.0.243) In the Perl script $R_HOME/bin/check there is a bug under the section "Check R code for syntax errors" where the 'Rfiles <- c(...)' is build up. If there are too many files in @Rfiles the source code line generated will be too long and weird things will happen, e.g. strange

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

Hi. I noticed that Brian Ripley found and corrected a bug in MinGW's ld.exe, see http://www.murdoch-sutherland.com/Rtools/. Thanks for this. I wonder if this is the same bug that cause my problems. I have tiny toy package with C code that installs perfectly on R Version 2.2.1 beta (2005-12-18 r36792) [this version was mislabelled "beta" the first few hours on CRAN when the stable

The trailing backslash seems to be the culprit. After looking at rw1020\bin\INSTALL, I noticed $pkg =~ s/\/$//; which I assume is to strip the trailing slash from a package name before obtaining the package name and cleaning out its directory I added $pkg =~ s/\\$//; immediately after this line. Rerunning Rcmd INSTALL C:\rw1011\src\library\bqtl\ with that change seemed to work OK

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

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 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

Hi all, I installed rw1031 but not uninstalled rw1030 just to make sure everything was working normally with the new version. After few weeks, I'm ready to uninstal rw1030. My question is: should I use the rw1030 unins00.exe program or could this program damage the rw1031 inatallation (perhaps modifies the registry...) ? Perhaps should I just delete the rw1030 directory? Thanks Dr.

Prof Brian Ripley wrote [22.01.2001]: > The code is new in 1.2.1, and identical code in Rcmd clean works. It looks > like a Windows Perl bug. On my machines under NT4 and 98 this works > because -d foo seems to be always true! It is probably different on 2000. > > Try changing the line > > unless (-d $TMPDIR); > > to > unless (-e $tmpdir); >

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

Hi, Gordon Smyth brought the following problem to my attention. PROBLEM/"BUG": Using R v1.9.0 alpha for Windows and the latest Rtools from Brian Ripley you get the following problem trying to R CMD build a package (or a bundle); >R CMD build R.basic * checking for file 'R.basic/DESCRIPTION' ... OK * preparing 'R.basic': * checking whether 'INDEX' is

Full_Name: Eugene Canjels Version: 1.3.0 OS: windows 98 Submission from: (NULL) (24.18.150.226) Help file "..\R\rw1030\doc\html\rwin.html" does not contain link to "..\R\rw1030\doc\html\function.html" as it did in R 1.2.3 Also within file "..\R\rw1030\doc\html\packages.html" links to individual packages don't work since they refer to the d: drive rather than

On Wed, 14 Aug 2002, Henrik Bengtsson wrote: > Sorry, but it was indeed the redirection of the standard output in > Cygwin/bash that cause the first problem, not R (I should stop doing > troubleshooting at 1:00 AM). So please forget about the problems reported in > R_CMD_check.out. However, it would still be nice if you still update R CMD > check to do join with "\n".

Hi All, I am having a problem with Rcmd build using R-devel on WinXP. If I try to build a package using the --binary flag, I get the following error: Error: cannot change to directory ' 'c:/TEMP/Rbuild.XXXX' ' Where XXXX is some number. I can get Rcmd build to work using R-1.7.1 and R-1.8.0, so I don't think it is a permission problem. I looked at the build file, and the

Hi All, I am having a problem with Rcmd build using R-devel on WinXP. If I try to build a package using the --binary flag, I get the following error: Error: cannot change to directory ' 'c:/TEMP/Rbuild.XXXX' ' Where XXXX is some number. I can get Rcmd build to work using R-1.7.1 and R-1.8.0, so I don't think it is a permission problem. I looked at the build file, and the

Hello, happy new year to all. The new Year gave me a new computer with Win98 and promptly I installed R on it. I created a directory R, with subdirectories gcc, perl,bin, helpwrk and rw1040. I got rw1040 from BDR place, the rest were gotter from the internet in the last week of the year, i.e. they are the newest versions. I modified autoexec.bat to put gcc\bin, perl\bin, etc in the path. I put the

A binary distribution of R-1.3.0 to run on Windows 95, 98, NT4.0 and 2000 on Intel/clone chips is available at http://sirio.stat.unipd.it/RWin It will be mirrored at a CRAN site near you in a couple of days. See below for a list of Windows-specific changes. guido masarotto (for the R-core team) Windows-specific changes to R =============================

Full_Name: David Firth Version: 1.2.3 OS: Windows NT4 Submission from: (NULL) (163.1.103.107) Two things that look like bugs: 1. RCMD INSTALL does not seem to cope with quotes in the Windows path. With my path set to PATH="C:\R\Rtools";"C:\R\rw1023\bin";C:\Perl\bin\;C:\WINNT\system32;C:\WINNT;C:\ mingw2\bin I get, for example, C:\R>RCMD INSTALL boot RCMD

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