search for: r_src

Hello, Using R 1051 in win98 When I try to build a library Addreg with DESCRIPTION, Index and Title in R and subdirectories Man and R. From a Command window I do: c:\> c:\rw1051\bin\Rcmd INSTALL c:\r_src\src\library\addreg --library=c:\r\src\library make: Entering directory '/cygdrive/c/rw1051/src/gnuwin32' make DLLNM= \ -C c:/r_src/src/library/addreg PKG=addreg RHOME=c:/rw1051 RLIB=c:/r_src/library \ -f c:/rw1051/src/gnuwin32/MakePkg make: make: Command not found make: *** [pkg-addreg]...

Hello, I am on win98 with R1.4 from BDR I have a directory structure like this c:\R\RW1040 c:\R\R_CRAN\Library C:\R\R_SRC\Library so Y put the new versions of R in RW... and I download the packages from CRAN into R=R_CRAN\library so they do not change from R version to version, R\R_SRC is for packages from other places than CRAN or for my own things Now if when R starts I say > library() I get the list of packages...

Default arguments are evaluated in the function frame, not in the calling environment (nor in the same place as explicit arguments). > Which to me reads that a with statement as above is equivalent to > > > attach(data) ; aov.SS1(y=Obs) ; detach(data) > > Or is that just wishful thinking?? The latter. On Thu, 7 Oct 2004, RenE J.V. Bertin wrote: > Hello, > >

I would like to compile for Windows a rather simple R package that contains some C code. It does not contain any Fortran code. I tried the cross-compilation route using the pre-built set of tools from http://www.devolution.com/~slouken/SDL/Xmingw32/, as described in $R_SRC/src/gnuwin32/INSTALL Using the sources in r-devel from the rsync site I am able to build libR.a in src/gnuwin32 but I can't build the package. Using the sources in r-release-patched from the rsync site I am unable to build libR.a. The tail end of that compilation log is $ cd r-release/src/...

Ravi Varadhan and I have been looking at UCMINF to try to identify why it gives occasional (but not reproducible) errors, seemingly on Windows only. There is some suspicion that its use of DBLEPR for finessing the Fortran WRITE() statements may be to blame. While I can find DBLEPR in Venables and Ripley, it doesn't get much mention after about 2000 in the archives, though it is in the R FAQ

Ravi Varadhan and I have been looking at UCMINF to try to identify why it gives occasional (but not reproducible) errors, seemingly on Windows only. There is some suspicion that its use of DBLEPR for finessing the Fortran WRITE() statements may be to blame. While I can find DBLEPR in Venables and Ripley, it doesn't get much mention after about 2000 in the archives, though it is in the R FAQ