similar to: 'R CMD build' fails when there are spaces in the path (PR#6830)

Full_Name: Steffen Version: 2-5-0 OS: Windows Submission from: (NULL) (192.124.243.162) Hi, the R CMD build script is using if($WINDOWS) { ## workaround for paths in Cygwin tar $filepath =~ s+^([A-Za-z]):+/cygdrive/\1+; } which does not work if the build environment is a MINGW. I have added the patch below, Yours, Steffen $ diff -u build build.orig --- build

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

R developers, I've been happily building packages, under windows, for some time now and upgraded to R 2.1.0 and now when I attempt to build a package, I get the following errors... C:\conifers>rcmd build Rconifers * checking for file 'Rconifers/DESCRIPTION' ... OK * preparing 'Rconifers': * checking DESCRIPTION meta-information ... OK * cleaning src * checking whether

Under Linux the cleanup script (if it exists) is run at the end, before the package archive is created, and this prevents intermediate files that are no longer needed from being written to the archive. Unfortunately, this does not happen under Windows when there is a cleanup.win. That is, cleanup.win is not run before the archive is created. Here is the code in build.pl that checks for cleanup

The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of

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

I tried to compile R-beta_2010-10-02_r53128 on FreeBSD 9.0-CURRENT (amd64) with gcc-4.4.5 and it fails: ----------------------------------------- gcc -std=gnu99 -I../../src/extra/zlib -I../../src/extra/bzip2 -I../../src/extra/pcre -I../../src/extra -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -g -O2 -c sysutils.c -o sysutils.o sysutils.c: In function

On 11/24/20 11:27 AM, Jan Gorecki wrote: > Thanks Bill for checking that. > It was my impression that warnings are raised from some internal > system calls made when quitting R. At that point I don't have much > control over checking the return status of those. > Your suggestion looks good to me. > > Tomas, do you think this could help? could this be implemented? I think

Dear Sir or Madam: This is an extension to a earlier post, about looping through several thousand files, and testing student's models against a different data-set, called rclnow, for "recall now". The problem is, that the instructor never specified to the students, what they should name their "lm" object. So what they created was: "arbitrary variable name"

Dear WizaRds, I wrote a small function in R and would like to create a package. The necessary documentation is done, Rtools etc. are installed and I am still unable to complete the process under Windows. I did extensive research in the archives and read the Murdoch-Sutherland website on the Rtools and MikTeX hints. I realize that I understand only half or less of what is said there

Yesterday I downloaded R-2.2.0.tar.gz, gunzipped and untarred, and did the usual ./configure and make. Everything seemed to go smoothly until it got to the bit about installing recommended packages. It got past ``spatial'' but turned up a fatal error in respect of the ``boot'' package. Here is some of what appeared on the screen:

Hi, I wonder about the reason for the following lines: $ diff ~/local/lib64/R/bin/build /usr/lib64/R/bin/build 40c40 < my $revision = ' $Rev: 46832 $ '; --- > my $revision = ' $Rev: 45803 $ '; 576,579d570 < if(-r "Makevars") { < $makefiles .= " -f Makevars"; < R_system("${R::Vars::MAKE}

Full_Name: Tom Short Version: 1.9.0 OS: Win2000 Submission from: (NULL) (64.65.255.41) POSSIBLE WISHLIST, POSSIBLE BUG: The following code works on Debian, but fails on Windows 2000 with 'Error in file("test.png", "r") : unable to open connection': bitmap("test.png") plot(c(1,2,3)) dev.off() x = file("test.png","r") The problem is

Dear R-developers, Some of the more fat scripts (50+ GB mem used by R) that I am running, when they finish they do quit with q("no", status=0) Quite often it happens that there is an extra stderr output produced at the very end which looks like this: Warning message: In .Internal(quit(save, status, runLast)) : system call failed: Cannot allocate memory Is there any way to avoid this

On Tue, 24 Nov 2020, Jan Gorecki wrote: > As for other calls to system. I avoid calling system. In the past I > had some (to get memory stats from OS), but they were failing with > exactly the same issue. So yes, if I would add call to system before > calling quit, I believe it would fail with the same error. > At the same time I think (although I am not sure) that new allocations

I have an R library which uses identify() and system(com="xterm -e less /a/corresponding/file") to view files when I click on an x11() plot. I can successfully resize the xterm on Linux (i486) and Macos 10.4 (G4 and G5), but NOT Macos 10.4 (Intel). For example, on a new mac pro: # in a terminal,xterm,iterm,etc: xterm -e "printenv | less" # the resulting xterm resizes

For embedded projects, one may want to eliminate the per-session temp directory created by InitTempDir() and just use a system-specific temp directory. Here's my solution: extern char *R_TempDir; void my_InitTempDir() { char *tmp; if (R_TempDir){ if (rmdir(R_TempDir) != 0){ perror("Fatal Error: could not remove R's TempDir!");

I just post it not to forget - will try to contribute a fix. Example: CDNmoney_2003.9-2.tar.gz (in the archives section of CRAN) [There is another problem here I'll address separately.] If running solely, R CMD check CDNmoney fails to detect a failed installation on Windows. Instead, it reports: * checking whether package 'CDNmoney' can be installed ... OK Of course, the check

Hi R-helpers, I am trying to build a package under FreeBSD 5.4-RELEASE #0 using R Version 2.1.1. I have constructed a package using package.skeleton(), when I try $ R CMD build foo * checking for file 'foo/DESCRIPTION' ... OK * preparing 'foo': * checking DESCRIPTION meta-information ... OK * cleaning src * removing junk files tar: Option -L is not permitted in mode -x Error:

I shouldn't try to do this on Monday morning. Can anyone suggest why the make for R 0.63 is failing for me under Solaris (SunOS 5.6). Paul Gilbert ... creating src/scripts/html2dos creating tests/Makefile creating tests/Examples/Makefile creating src/include/Platform.h R is now configured for sparc-sun-solaris2.6 Source directory: . Installation directory: /usr/local C