search for: pkgdirs

(Warning: There is some potential that this message is redundant.) I think that i have spotted an issue with R CMD check that does not trace back to a rare case, so it must have been reported already or i am doing something stupid. However, to be sure and because I did not find any comments on this while searching the R mailing lists, here is what i did: R CMD check . from within a package

It appears that file.copy() does not protect against the case when one copies one directory to a subdirectory of itself resulting in it trying to create and endless recursive copy of itself. REPRODUCIBLE EXAMPLE: src <- "foo" dir.create(src); file.copy(src, src, recursive=FALSE) # ok file.copy(src, src, recursive=TRUE) # PROBLEM

Dear All: I encountered and apparently overcame problems following Yan and Rossini?s procedure for "Building Microsoft Windows Versions of R and R packages under Intel Linux" (http://cran.r-project.org/doc/contrib/cross-build.pdf): I have successfully cross-compiled R packages for Windows on a FreeBSD 4.10 i386 system. My revisions to Makefile-rcb (http://cran.r-

Hello All, Attached is a patch makes the following changes to contrib/aix relative to 3.1p1: * Gets version number from ssh -V as suggested by Tim Rice. * Does a better job of generating valid AIX package version numbers (fixes inutoc "format of the toc file is invalid" and "invalid level" errors reported by Mandar Mirashi). * Tests for "make install" failure and

Hello All, This is a resend of a patch I posted nearly two weeks ago. As of a few minutes ago, it hasn't been committed and thus the AIX package builds from CVS fail. (I know because I now have a cron job that tells me :-) Could someone please review and commit the attached patch and chmod a+x contrib/aix/*.sh, or let me know what needs to be changed? It makes the following changes

Dear All, I have tried to install the tensor package (from: http://cran.r-project.org/src/contrib/PACKAGES.html#tensor ), using the comand: " shell("Rcmd INSTALL tensor") " then I got the following mensage: ---------------------------------------------------------------------------------- make: Entering directory `/d/bin/cran/rw1022/src/gnuwin32' make DLLNM= EXTRADOCS= \

...eak the build entirely. What are the actual options for --docs=TYPE? I have tried all the documentation sources I know of, plus hacking the perl code, but can't see what the options are. Thanks Gordon For easy reference, here is the help output from rcmd build: Usage: Rcmd build [options] pkgdirs Build R packages from package sources in the directories specified by pkgdirs. Options: -h, --help print short help message and exit -v, --version print version info and exit --force force overwriting of (index) files --no-vignettes do not rebu...

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.

Hi all I am trying to package a library in R 1.6.1 (Windoze XP). I have read the document "Writing R extensions" and think I have done things correctly (though apparently not). I have searched the mail archives for help to no avail. I also posted a few days ago and thanks to Peter Dalgaard I have managed to focus my search for errors. I am trying to create a library in R. I run the

Dear R-helpers, I'm learning how to compile R packages with fortran routines and use the acepack source as an example. After some hiccups (Guido told me about the need to set make_mode=UNIX) I got to the following: `make pkg-acepack' runs without error (see below), but it does not * compile any .f file in acepack/src * (hence) try to create any dll file or libs (I'm

I was trying to learn cross building an R pcakage for windows on my linux machine. I picked a relatively small library gee to test. I downloaded the cross-tools and put them in my path, jyan at ludwig:/a3/jyan/src/R-1.2.1/src/gnuwin32$ echo $PATH /home/jyan/cross-tools/bin:/home/jyan/cross-tools/i386-mingw32msvc/bin: /usr/lib:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games Following the

tools::R_user_dir() provides configurable directories for R packages to write persistent information consistent with standard best practices relative to each supported operating systems for applications to store data, config, and cache information respectively. These standard best practices include writing to directories in the users home filespace, which is also specifically against CRAN policy.

Hello, The change in release number broke some some assumptions in buildbff.sh: * SSH_VERSION was always on the last line of version.h * The OpenSSH version number would give a valid installp version (which must have four parts). Thanks to Mandar Mirashi for pointing this out. Anyone affected can try the following patch which works for me and hopefully will behave sanely in future. -Daz.

This bug appears in the current Windows build; I don't know if it applies generally. Duncan Murdoch On Fri, 26 Sep 2003 15:25:57 +1200 (NZST), Ray Brownrigg <ray@mcs.vuw.ac.nz> wrote: >If you INSTALL (Rcmd INSTALL) or cross-compile >(make PKGDIR=/pkg RLIB=/library pkg-mypkg) the copying of the inst >directory seems to happen very early in the process, *before anything is

This bug appears in the current Windows build; I don't know if it applies generally. Duncan Murdoch On Fri, 26 Sep 2003 15:25:57 +1200 (NZST), Ray Brownrigg <ray@mcs.vuw.ac.nz> wrote: >If you INSTALL (Rcmd INSTALL) or cross-compile >(make PKGDIR=/pkg RLIB=/library pkg-mypkg) the copying of the inst >directory seems to happen very early in the process, *before anything is

...nd TEMP) to > C:\Temp, > and try to run the whole thing from a "DOS" Cmd.exe window. Here it is: D:\dirk\bands\implementation>set TMPDIR=d:\tmp D:\dirk\bands\implementation>echo %TMPDIR% d:\tmp D:\dirk\bands\implementation>r CMD BUILD --help Usage: R CMD BUILD [options] pkgdirs Build R packages from package sources in the directories specified by pkgdirs. Options: -h, --help print short help message and exit -v, --version print version info and exit --force force overwriting of INDEX file --no-vignettes do not rebuild...

Had some fun today, and thought it might be a good idea to share and possibly for inclusion to R/src/gnuwin32/README.packages . Wine/linux : while R, ActiveState Perl, mingw all works alright under wine, the blocking issue is Rtool's cygwin dependency. forking (as much of make and sh is forking sub-processes) on posix-on-win32-on-posix currently doesn't work.

I am compiling the latest R-patched (Revision: 65533) Ubuntu Lucid (10.04). Building succeeds but make check stops with an error. The output in the terminal from make check: Testing examples for package ?base? Testing examples for package ?tools? Error: testing 'tools' failed Execution halted make[3]: *** [test-Examples-Base] Error 1 make[2]: *** [test-Examples] Error 2 make[1]: ***

A binary distribution of R 0.90.1 is available at http://www.r-project.org/bin/windows/windows-NT/base/ Installation instruction are given in the README file at the same location. guido masarotto Windows changes since 0.90.0 ---------------------------- It is possible to install packages from any directory (set PKGDIR on the make command) and to any directory (set RLIB on the make

A binary distribution of R 0.90.1 is available at http://www.r-project.org/bin/windows/windows-NT/base/ Installation instruction are given in the README file at the same location. guido masarotto Windows changes since 0.90.0 ---------------------------- It is possible to install packages from any directory (set PKGDIR on the make command) and to any directory (set RLIB on the make