similar to: R v1.9.0 alpha w/ Rtools: gzip problem

The following is a patch (svn diff) for the R CMD build script that calculates exclude patterns after the tar/untar step rather than before. The perl find() function, used in the calculation of the exclude patterns, ignores symlinks, which meant that directory symlinks were not considered for exclusion. Since the tar/untar step resolves (copies) symlinks, this works around that limitation.

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 *

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, I'm running R v1.9.0 on WinXP Pro. I noticed that R.exe and Rterm.exe behave differently on Ctrl-C. Starting a Windows Command prompt (cmd.exe) you get from running Rterm.exe: C:\Program Files\R>rw1090\bin\Rterm.exe --vanilla --quiet > ^C > ^C > 1+1 [1] 2 > Sys.sleep(100) # Ctrl-C after a few seconds > ^C > ^C > 1+1 [1] 2 > q() C:\Program Files\R>

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, I was just looking at the "CRAN Daily Package Check Results" [http://cran.r-project.org/src/contrib/checkSummary.html], and realized there are 1000 packages on CRAN as of today (look at row 3 in the table below). Yet another quite extraordinary milestone in R history. Last updated on 2007-04-12 11:48:32 Results for installing and checking packages using the three current flavors

I don't know if this is the correct forum to ask the following question; however, when I search the aroma.affymetrix discussion group, it suggested that I should posted the question to r-help. Here it goes. I followed the instructions on aroma.affymetrix trying to install the packages; following are the steps: > install.packages(c("R.oo", "R.utils"),

Full_Name: Henrik Bengtsson Version: rw1022 OS: Windows Me Submission from: (NULL) (216.175.126.55) When ${R_HOME}/share/perl/maketitle.pl tries to generate a TITLE that is longer than $lc-3 (=13) characters long, it repeats the package name on line two. Example: Now it generates an output like: com.braju.graphics com.braju.graphics Bla bla bla... But, I believe it should

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

Hi, I've got a version of rowMedians(x, na.rm=FALSE) for matrices that handles missing values implemented in C. It has been optimized for memory and speed. To avoid coercing integers to doubles, and hence allocate an additional 200% memory, there is one C function for integers and one for doubles. The rowMedians() implementation is currently sitting in my non-CRAN package R.native

Full_Name: Henrik Bengtsson Version: 1.3.0 OS: Windows Me Submission from: (NULL) (216.175.122.171) I realized that the title of packages in the library index when they are in a bundle is the title of the bundle and not the package. It looks like the TITLE file, which apparently is used for generating the library index, takes the value of the bundle's title and not the package's title.

Full_Name: Yoon, hye sung Version: 1.8.1 OS: window Submission from: (NULL) (203.255.177.155) > library(sna) Warning message: package sna was built under R version 1.9.0 > What's this message mean?

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

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

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

I have build asterisk from latest CVS HEAD-05/09/05 with H323 support as described in README file. Open H.323 version v1.17.1 and PWLib v1.9.0 on Mandrake Linux 10.2 kernel-2.6.11 I tested it with following phones: -- XLite (SIP softphone) -- QMix SIP IP phone (PA168F) -- SJPhone (H323 softphone) -- QMix H323 IP phone (PA168F) -- FireFly (IAX2 softphone) Everything works fine except a problem

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

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

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}

I'm attempting to use xyplot() within a for() loop to plot the relationship between a DV and a series of predictor variables, split by 2 conditioning variables. However, xyplot() does not "seem" to be recognized within the for() loop; I don't receive any error message, but nothing is plotted and a plotting device is not opened. When I use the generic function plot(),