similar to: install

I'm trying to install version 0.63.2 on an SGI Origin 200 with plenty of memory, running Irix 6.5. I previously installed 0.63.0 on this same system without incident. I'm getting the following error when I run ./configure: creating cache ./config.cache checking for a BSD compatible install... /usr/local/bin/ginstall -c checking whether ln -s works... yes checking for ranlib... ranlib

[[0.62.3, already 0.62.2]] This bug report is overdue, but I really didn't test these things for weeks (have always used gcc, but only yesterday, someone told me that he saw a speed gain of a factor 2 when using Sun's cc over gcc) I just found that the same problem is already in 0.62.2 If I take yesterday's R-release.tar.gz (or also R-0.62.2.tar.gz) unpack and add CC=cc -----

useR's, I want to apply this function to the columns of a data frame: u[u >= range(v)[1] & u <= range(v)[2]] where u is the n column data frame under consideration and v is a data frame of values with the same number of columns as u. For example, v1 <- c(1,2,3) v2 <- c(3,4,5) v3 <- c(2,3,4) v <- as.data.frame(cbind(v1,v2,v3)) uk1 <- seq(min(v1) - .5, max(v1) + .5,

When I run configure for the new release, R-0.63, I get an error: loading cache ./config.cache checking for a BSD compatible install... aux/install-sh -c checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... bison -y checking for ar... ar checking for ratfor... no checking for latex... /psoft/TeX/bin/latex checking for dvips... /psoft/TeX/bin/dvips checking for

When I run configure for the new release, R-0.63, I get an error: loading cache ./config.cache checking for a BSD compatible install... aux/install-sh -c checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... bison -y checking for ar... ar checking for ratfor... no checking for latex... /psoft/TeX/bin/latex checking for dvips... /psoft/TeX/bin/dvips checking for

Running R.app on Mac OS X 10.4 > version _ platform powerpc-apple-darwin8.6.0 arch powerpc os darwin8.6.0 system powerpc, darwin8.6.0 status major 2 minor 3.1 year 2006

Running R.app on Mac OS X 10.4 > version _ platform powerpc-apple-darwin8.6.0 arch powerpc os darwin8.6.0 system powerpc, darwin8.6.0 status major 2 minor 3.1 year 2006

I installed the locfit package under Linux (gcc 2.7.2). Installation was ok but > x <- runif(200) > y.compl <- 10*x*x*rgamma(200,3) > med.y <- median(y.compl) > cens <- ifelse(y.compl<=med.y,1,0) > y <- cens * y.compl + (1-cens)*med.y > library(locfit) > m <- locfit(y~x,cens=cens,family="gamma") /usr/local/src/R-0.61.1/bin/R.binary: can't

Dear useRs and wizaRds, I am currently developing a set of functions using S4 classes. On the way I encountered the problem exemplified with the code below. For some reason the 'validity' method does not seem to work, i.e. does not check for errors in the specification of the slots of the defined class. Any hints? My understanding of the whole S4 system was that validity checks are made

This is a simple SSA code generation 101 question. If I follow the IR code generation techniques in the Dragon book the statement x = y + z would translate into something like this in SSA/LLVM %0 = add %y, %z %x = %0 Obviously "copy instructions" like %foo = %bar are senseless in SSA since %foo and %bar are immutably fixed to the same value and there is no need for two aliases

Hi everyone! I have a Digium Card TDM410 But, it appear for me this massege chan_dahdi.c:8061 handle_alarms: Detected alarm on channel 3: Red Alarm But my line is ok! But sometimes it back sig_analog.c:3807 analog_handle_init_event: Alarm cleared on channel 2 But it again back to red alarm. What can be happen? My lines is all ok! But when I put on Digium Card TDM410 is very inconsistent

Would introducing the new frame, with the call to local(), cause problems when you use frame counting instead of <<- to modify variables outside the scope of lapply's FUN, I think the frame counts may have to change. E.g., here is code from actuar::simul() that might be affected: x <- unlist(lapply(nodes[[i]], seq)) lapply(nodes[(i + 1):(nlevels - 1)],

From: Daniel Kaschek <daniel.kaschek at physik.uni-freiburg.de> > ... When I evaluate this list of functions by > another lapply/sapply, I get an unexpected result: all values coincide. > However, when I uncomment the print(), it works as expected. Is this a > bug or a feature? > > conditions <- 1:4 > test <- lapply(conditions, function(mycondition){ >

Hi, when i run the following code i get this massege: "The instruction at 0x######## reference memory at 0x#######, the memory cannot be "read". and then i have to close R. what is the problem and how can i solve it? thanks in advance Avi my code # frailtypack library(frailtypack) cgd.ag <- read.csv("C:/rfiles/RE/cgd.csv") cgd.nfm <-frailtyPenal(Surv(TStart,

It is my understanding, the alloca memory routines are used for forcing variables to be allocated on the stack frame -- which you would want for source level debugging. When SSA registers are used, LLVM will decide what goes into registers and what will spill over to the stack frame. I want the latter. --w Wayne O. Cochran Assistant Professor Computer Science wcochran at vancouver.wsu.edu

I have an application where I need to preserve object attributes across calls to 'lapply'. The current definition is: lapply <- function (X, FUN, ...) { FUN <- match.fun(FUN) if (!is.list(X)) X <- as.list(X) rval <- .Internal(lapply(X, FUN)) names(rval) <- names(X) return(rval) } Would it make sense to replace names(rval) <- names(X)

> On Feb 24, 2015, at 10:50 AM, <luke-tierney at uiowa.edu> wrote: > > The documentation is not specific enough on the indented semantics in > this situation to consider this a bug. The original R-level > implementation of lapply was > > lapply <- function(X, FUN, ...) { > FUN <- match.fun(FUN) > if (!is.list(X)) > X <-

Source: xen Version: 4.0.1-2 Severity: serious Tags: wheezy sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20110313 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory `/build/user-xen_4.0.1-2-amd64-2x64p6/xen-4.0.1/debian/build/build-docs/docs' > latex

I'd like to learn the process of revising R functions & packages and then submitting proposed patches to the R Core team. Would someone be willing to mentor me through one example? For starters, consider an example. I'd like to revise the t.test function to return the stderr value to the user. We only need to change the "rval" in the third-from-the end line of

Dear all, I'm using zeroinfl() from the pscl-package for zero inflated Poisson regression. I would like to calculate (aproximate) prediction intervals for the fitted values. The package itself does not provide them. Can this be calculated analyticaly? Or do I have to use bootstrap? What I tried until now is to use bootstrap to estimate these intervals. Any comments on the code are welcome.