similar to: file separator inconsistencies on windows?

Hi, I'm trying to register my native routines using R_registerRoutines (...). I can compile the code, but the loader cannot resolve the symbol: undefined symbol: _Z18R_registerRoutinesP8_DllInfoPK12R_CMethodDefPK15R_CallMethodDefS3_S6 _ $ nm bgx.Rcheck/bgx/libs/bgx.so | grep R_registerRoutines U _Z18R_registerRoutinesP8_DllInfoPK12R_CMethodDefPK15R_CallMethodDefS3_S6

Hi, R 2.5.0 isn't auto-completing paths properly as it used to. E.g. suppose I have: > dir("CEL/choe") [1] "chipC-rep1.CEL" "chipC-rep2.CEL" "chipC-rep3.CEL" "chipS-rep1.CEL" [5] "chipS-rep2.CEL" "chipS-rep3.CEL" Now if I do: ReadAffy("CEL/choe/ch<tab> # => ReadAffy("CEL/choe/chip

Dear all, R on Macports relies on GCC 4.3 to build packages. I find that packages with shared objects that use C++ streams crash R if they're compiled using Macports' gcc43, but work fine if compiled in exactly the same way using Apple-supplied GCC 4.2. Has anyone here had the same issue/know what is causing this problem? Thanks, Ernest

Dear all, I have wrapped a C++ function in an R package. I allocate/deallocate memory using C++ 'new' and 'delete'. In order to allow user interrupts without memory leaks I've moved all the delete statements required after an interrupt to a separate C++ function freeMemory(), which is called using on.exit() just before the .C() call. I am concerned about the

Hi all, I have some C++ code that I call from my package. In my main C++ loop, I check for user interrupts and return to the R shell after ensuring I've deallocated memory appropriately. This works fine when the code is compiled with gcc+openmp and with icc without openmp, but when I compile with icc and use openmp, the entire R session is immediately terminated when I hit ctrl-C. This

It seems unlink doesn't work with wildcards in 2.5.0. I've tried R-2.5.0 under gnu/linux from source and the Mac binary from att research. Example: > dir() [1] "bgx.Rnw" "bgx.pdf" "run.1" > unlink("run.*",recursive=T) > dir() [1] "bgx.Rnw" "bgx.pdf" "run.1" > unlink("run.1",recursive=T)

Why is it that R places CFLAGS after PKG_CFLAGS and not before when compiling a package (e.g. through R CMD build pkg)? This can be problematic if, for instance, you want to use -O3, but -O2 is in R_HOME/etc/Makeconf. If -O2 (in CFLAGS) appears after -O3 (in PKG_CFLAGS), you are left with what you didn't want: -O2. In R-exts, it says that "Flags which are set in file etc/Makeconf

Dear all, I have a code chunk in my Rnw file that, when executed, outputs carriage return characters ('\r') to inform on the progress (e.g. "sweep 4 of 1024\r"). But Sweave interprets this as a newline character, and therefore I get countless pages of output in my vignette where I only really want one line. Any ideas? Thanks E

The other day I was working on an example which used tempfile() to create file for use by the graphics device. And while I love tempfile()---as it is portable and clever and the files get cleaned by R and all that---I noticed one missing feature I would like to see: beside a starting name pattern, and an optional directory, an 'file extension' argument would be nice to have. As e.g. in

I was writing Rd documentation for a new package when I came across this issue. Here's the smallest example: > library(tools) > cat("\\examples{x <- '<%=rnorm(1)%>'}\n",file=file.path(tempdir(),'test.Rd')) > readLines(file.path(tempdir(),'test.Rd')) [1] "\\examples{x <- '<%=rnorm(1)%>'}" >

?tempdir says By default, ?tmpdir? will be the directory given by ?tempdir()?. This will be a subdirectory of the temporary directory found by the following rule. The environment variables ?TMPDIR?, ?TMP? and ?TEMP? are checked in turn and the first found which points to a writable directory is used: if none succeeds ?/tmp? is used. Unfortunately, it doesn't seem to

>>>>> Dirk Eddelbuettel <edd at debian.org> >>>>> on Sun, 23 Apr 2017 09:15:18 -0500 writes: > On 21 April 2017 at 10:34, frederik at ofb.net wrote: > | Hi Mikko, > | > | I was bitten by this recently and I think some of the replies are > | missing the point. As I understand it, the problem consists of these > |

Hello R-Help I have a question about the "behind the scenes" behaviour of the Rscript -e command and particularly its interaction with Sweave and tempdir(). We are trying to deploy R as a web service to do water quality analyses and have been writing software to call Sweave via Rscript eg: cmd> Rscript -e Sweave('sweavefile.Rnw') One problem we have been having is that

On 26/04/2017 4:21 AM, Martin Maechler wrote: >>>>>> <frederik at ofb.net> >>>>>> on Tue, 25 Apr 2017 21:13:59 -0700 writes: > > > On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote: > >> Might this combination serve the purpose: > >> * R session keeps an open handle on the tempdir it creates, >

Full_Name: Tom Callaway Version: 2.7.2 OS: Fedora 10 (Linux/x86_64) Submission from: (NULL) (96.233.67.230) Recently, Debian identified a security issue with the javareconf script in R. I confirmed that this is still unfixed in R 2.7.2. The following patch resolves the issue: diff -up R-2.7.2/src/scripts/javareconf.BAD R-2.7.1/src/scripts/javareconf --- R-2.7.2/src/scripts/javareconf.BAD

I was looking at the CRAN package 'bfork-0.1.2', which exposes the Unix fork() and waitpid() calls at the R code level, and noticed that the help file example for bfork::fork removes R's temporary directory, the value of tempdir(). I think it happens because the forked process shares the value of tempdir() with the parent process and removes it when it exits. This seems like a

Hi, all. I noticed recently that llvm::sys::fs::createTemporaryFile does not use llvm::sys::path::system_temp_directory, instead relying on its platform-specific helper TempFile. Is there any reason for this disparity? The two implementations are not in sync, either: - TempDir honors TMPDIR, TMP, TEMP, TEMPDIR, and a configuration-settable P_tmpdir on Unix-y systems. system_temp_directory just

This is great. Thank you for your help, but let me make sure I fully understand. Here is the looping file I use to subset the data frame, create a tex file, and Sweave it. This results in N number of tex files where N is equal to the number of rows in the data frame. list <- unique(wide$stuid) master = "master.tex" for (i in list){ tmp1 <- subset(wide, stuid==i) tmp2

Harold, I've taken a closer look at your example and I'd call this an Sweave bug. It creates tempfiles each time you run it, and doesn't delete them at the end. For example: > list.files(tempdir()) character(0) > testfile <- system.file("Sweave", "Sweave-test-1.Rnw", package = "utils") > Sweave(testfile, out="junk.tex")

>>>>> Jeroen Ooms <jeroenooms at gmail.com> >>>>> on Tue, 25 Apr 2017 15:05:51 +0200 writes: > On Tue, Apr 25, 2017 at 1:00 PM, Martin Maechler > <maechler at stat.math.ethz.ch> wrote: >> As I've found it is not at all hard to add an option >> which checks the existence and if the directory is no >>