similar to: patch: allow R CMD build exclude patterns to match symlinks

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

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

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

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

Full_Name: Byron Ellis Version: R 1.9.0 (and 2.0.0) OS: Linux (Redhat Fedora Core) Submission from: (NULL) (140.247.241.197) It appears that `R CMD build` cannot handle spaces in the path when building packages for distribution. For instance: [ellis@net-78815 ~/Bayesian Networks]$ R CMD build bnsl * checking for file 'bnsl/DESCRIPTION' ... OK * preparing 'bnsl': * cleaning src *

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

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? On Mon, Nov 23, 2020 at 7:10 PM Bill Dunlap <williamwdunlap at gmail.com>

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

I am working on the r panel package. Now if i have a function that uses a radiogroup button, and if i attempt to run the function from inside the rpanel menu, i get this error: Error in panel$intname : $ operator is invalid for atomic vectors However if i run the function per se i.e. not from inside the rpanel menu, but by calling it independently, the above error doesn't appear. Here is a

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 made in R are working fine. So R seems to reserve some memory and

Thank you for your help. I??m sorry that I found not the right entries in the R-devel. Now, I have again a problem. After installing all needed things I have run Rcmd INSTALL -l ../mypkg and respectively make mypkg By running Rcmd check I get following message: * checking for working latex ...Error: environment variable TMPDIR not set (or set to unusable value) and no default

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

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"

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 think you had to be using an install log to get that message. It is true that R_system($cmd) is not returning an error code, and I've fixed that. On Thu, 15 Apr 2004 ligges@statistik.uni-dortmund.de wrote: > 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

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:

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: