similar to: lme4 fails to install on R-1.9/FreeBSD-5.2 (PR#7007)

I am building from source on RHEL 4 and have run into a problem while running "make check": running code in 'lapack.R' ...make[3]: *** [lapack.Rout] Error 1 make[3]: Leaving directory `/opt/R/R-2.9.1/tests' make[2]: *** [test-Specific] Error 2 make[2]: Leaving directory `/opt/R/R-2.9.1/tests' make[1]: *** [test-all-basics] Error 1 make[1]: Leaving

Dear R developers, The trace of the hat matrix H~(n,n) is computed as follows: tr(H) = tr(BS^-1B') = tr(S^-1B'B) := tr(X) = sum(diag(X)) with B~(n,p), S~(p,p). Since p is of the order 10^3 but S is sparse I would like to employ Taucs linear solver ( http://www.tau.ac.il/~stoledo/taucs/ ) on SX = B'B. (Further improvement by implying a looping over i=1,...,p, calling

It is very useful to have svn version number encoded in llvm-gcc's -- version output. Here is one approach. Anyone has a better patch ? - Devang Index: Makefile.in =================================================================== --- Makefile.in (revision 53385) +++ Makefile.in (working copy) @@ -802,6 +802,9 @@ DEVPHASE_s := "\"$(if $(DEVPHASE_c),

I recently uploaded a developmental version of the Matrix package, Matrix_0.6-1.tar.gz, to CRAN where it is in the src/contrib/1.9.0/Other directory. It requires some of the packages that will appear in R-1.9.0. This version marks a major redesign of the Matrix package to use S4 classes and methods and to incorporate sparse matrix manipulations using routines from TAUCS

Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) (LLVM rXXXX)" Where you set the revision number? We currently use LLVM_VERSION_INFO to set this sort of information and to me it makes more sense to have the svn rev number there instead of just saying LLVM build like it does now. -Tanya On Wed, 9 Jul 2008, Devang Patel wrote: > It is very useful to have svn

I'd like to substitute the Subversion revision number for a string in a package man page every time the package is installed or built. I can assume it is being installed or built from a Subversion working copy. I tried putting a target that depends on FORCE into Makefile or Makevars in the src directory, but it is not being built. What sort of make magic do I need, and where do I put it

Dear developers, today I tried to build and install R-devel_2009-01-10 on FreeBSD 8.0-CURRENT (i386) for testing purposes. All went well until compiling the now recommended (integrated) Matrix package. At this point the following break occured: ------------------------------------------------ begin installing recommended package Matrix * Installing *source* package 'Matrix' ... **

On Jul 9, 2008, at 6:13 PM, Tanya M. Lattner wrote: > > Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) > (LLVM > rXXXX)" > > Where you set the revision number? I do not want to set the revision number in a source file every time I do 'svn update' :) > We currently use LLVM_VERSION_INFO to set this sort of information > and to

Dear R users I have started to use gdb for debugging dynloaded C code as described in `Writing R Extensions'. Unfortunately I have run into several problems that I haven't been able to solve: - using `n': how comes that the same line of code appears up to three times (and inbetween the next line and maybe even the second next one?) - using `print' resp. `display': How

{message bounced because it has "$$$" in it. manually approved by list maintainer -- MM} > Date: Tue, 22 Feb 2000 13:03:35 +0100 > From: jens <jniesch at gwdg.de> > > I have trouble to install R on Sparc Sun Solaris 2.6. > make returns the error message: > Undefined symbol first referenced in file > d_lg10 ../appl/libappl.a(uncmin.o) > d_sign

I am having trouble using Jim Lindsey's libraries because of unresolved symbols. I am currently using R 0.65.0, but had this problem in earlier releases as well. I have a RedHat 6.0 Linux on i386 and use egcs (upgraded to that distributed with rawhide, after first failures with the libraries): egcs-g77-1.1.2-19 egcs-1.1.2-19 Installation of the libraries works but on loading >

Recently I reviewed my RPM spec files for DU 4.0, and noticed that I forgot to post some problems + patches: 1. ./configure fails to choose a PIC flag, I simply removed the AC_MSG_ERROR and it works. There is actually no PIC flag for DEC cc (with DU 4.0E) --- ./configure.in.alpha-patch Mon Aug 23 06:36:28 1999 +++ ./configure.in Sun Sep 12 17:38:27 1999 @@ -541,7 +541,9 @@

I have been trying to compile R. I downloaded R-1.0.1.tgz(I think; the original tar file was untarred) and unpacked it with gzip. Now all the R files are in a directory named R-1.0.1. The source files (.c) are in R-1.0.1/src. There are files in R-1.0.1 named 'Makefile.in', 'Makeconf.in', and 'Makeconf'. I followed the instructions in INSTALL by typing

R fails to build with visibility on and gcc 4.9's link time optimzation, because of its practice of building part of it as archive first. Specifically it builds some bundled libraries as archive first, the symbols of which are then entirely invisible in gcc 4.9. The Matrix package also does this awful practice, with CHOLMOD.a COLAMD.a AMD.a SuiteSparse_config.a . One way of fixing R is:

This seems to be a problem that goes back a long time - and I hope someone who understands what tre is suppossed to be doing will look at this. A short history of other people who have reported on this on different versions of AIX. I shall only add that I get the same results on AIX 5.3 TL7, AIX 6.1 TL9 and AIX 7.1 TL3. Basically, with settings that work for AIX and 32-bit - the only changes

Hi, This is Kotien Wu from NIH/NCI. We want to use R function for our web: http://cgap.nci.nih.gov It works for functions in R/R-1.9.1/src/nmath/standalone very well. We have function GetPvalueForT.c which has #define MATHLIB_STANDALONE 1 #include <Rmath.h> double GetPvalueForT ( double t, double deg ) { return 2 * pt(t, deg, 0, 0); } We create GetPvalueForT.i, which has /* File :

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

Hi We are currently embedding a rather large C++ library in R (BioC), and we want some comments on the portability of how we have approach this. First of, we are not really able to do much about the portability of the basic library, which of course is the main question :) We have an approach which seems to work, I just want a bit of feedback on it.... The way we integrate it into R is

Hi This is a question prompted by the mac version of R, but as I see it, it should have broader interest. These days the CRAN Mac binary per default compiles every package for two architectures. First i386 and then ppc. In between the two compilation runs, any object files in pkgname/src is removed. This cleanup is necessary since otherwise Make would not recompile the object files

On Jul 9, 2008, at 6:13 PM, Devang Patel wrote: > > On Jul 9, 2008, at 6:13 PM, Tanya M. Lattner wrote: > >> >> Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) >> (LLVM >> rXXXX)" >> >> Where you set the revision number? > > I do not want to set the revision number in a source file every time I > do 'svn