similar to: Cannot make 3 different R installations for 3 different valgrind-instrumentation levels

"R Installation and Administration", section 2.5 "Sub-architectures" describes calling specific builds of R using the call "R --arch=name". I am trying to build and install three versions of R-2.9.1, each configured with a different valgrind-instrumentation level ("Writing R Extensions", section 4.3.2 "Using valgrind"). My goal is to be able to

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 developeRs, I'm trying to build R (2.7.1, on an x86_64 running Linux, but I believe I have observed this on x86 and with earlier versions of R as well) using external BLAS and LAPACK libraries _and_ generating libR.so, libRblas.so and libRlapack.so. Without --enable-BLAS-shlib, configure is able to find and use the external LAPACK library: ./configure \

Hi, I was trying to install package glmnet in R, but failed and it show such messages: * Installing *source* package glmnet ... This package has only been tested with gfortran. So some checks are needed. R_HOME is /home/username/R/R-2.9.0 Attempting to determine R_ARCH... R_ARCH is Attempting to detect how R was configured for Fortran 90.... Unsupported Fortran 90 compiler or Fortran 90

Full_Name: Murray Stokely Version: 2.10.1 OS: Linux Submission from: (NULL) (216.239.45.4) The Defn.h header includes limits.h for PATH_MAX and then checks if it hasn't been defined and if not sets something manually. Some of the R code uses PATH_MAX but a lot of other functions in unix/sys-unix.c and main/startup.c just hardcodes a limit of 256 characters. In my environment this is not

Hello I have a Mac OS X 10.4.5. I am trying to build a 64-bit R by following the directions on this page: http://r.research.att.com/building.html r_arch=x86_64 \ CC="gcc -arch x86_64 -std=gnu99" \ CXX="g++ -arch x86_64" \ OBJC="gcc -arch x86_64" \ F77="gfortran -arch x86_64" \ FC="gfortran -arch x86_64" PATH=/usr/X11/bin:/usr/local/bin:$PATH

Hi, is there any chance to install glmnet with gcc-4.5.2? For me it fails on all systems with: trying URL 'http://mirrors.softliste.de/cran/src/contrib/glmnet_1.7.tar.gz' Content type 'application/x-gzip' length 522888 bytes (510 Kb) opened URL ================================================== downloaded 510 Kb * installing *source* package ?glmnet? ... This package has only

First I tried 'setenv R_SHELL /usr/local/bin/bash', as bash is the weapon of choice for the faculty wishing to use R, then ran ./configure as before. The ./configure output line using as R_SHELL for scripts ... /usr/local/bin/bash would seem to indicate that the R_SHELL environment variable was recognized and acknowledged. However, I got the same build error: gnumake[2]: Entering

Dear R-Devel, I'm using Ubuntu on an x86_64 machine and would like to have both the 32-bit and 64-bit versions of R built from source. By default, following the usual build procedures yields 64 bit R. Looking at [these](http://cran.r-project.org/doc/manuals/R-admin.html#Sub_002darchitectures), I thought I could build 32-bit R by executing r_arch=32 ./configure and building R like usual

https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=16660 Here is the bug, which R.home may generate a path contains a whitespace. this will cause Rcpp failed executing sourceCpp > sourceCpp("b:/2018-12-14/src/18020/MCMC.cpp") Error in system(cmd, intern = !showOutput) : 'D:/Program' not found Error in system(cmd, ignore.stderr = TRUE, intern = TRUE) :

On 11/09/2019 21:38, Berend Hasselman wrote: > The Lapack library is loaded automatically by R itself when it needs it for doing some calculation. > You can force it to do that with a (dummy) solve for example. > Put this at start of your script: > > <code> > # dummy code to get LAPACK library loaded > X1 <- diag(2,2) > x1 <- rep(2,2) > # X1;x1 > z <-

Le 27/09/16 ? 13:31, Dirk Eddelbuettel a ?crit : > > On 27 September 2016 at 09:37, Eric Deveaud wrote: > | Hello, > | > | I'm tring to install a Rpackage that holds some C//C++ code > | > | as far as I understood the R library generic compilation mechanism, > | compilation of C//C++ sources is controled > | > | 1) at system level by the ocntentos

Line 1204 (right now) of svn/r-devel/doc/manual/R-exts.texi has dest <- file.path(R_PACKAGE_DIR, paste0('bin', R_ARCH) which lacks a closing ) -- two open, only one close right now. Dirk [1] I would have reported a bug, but I am aware of a recent and not-so-friendly response when bugzilla was used to report a typo. -- http://dirk.eddelbuettel.com | @eddelbuettel | edd at

Hi Matt Your method is the easiest way for me to install the 64-bit R. I followed the directions on your web site and then did the following: R --arch=x86_64 source("http://bioconductor.org/biocLite.R") biocLite(type = "source",lib = "/Library/Frameworks/R.framework/Versions/2.8/Resources/RLib64") I got many errors and warnings which I copied to the attached file.

Hello, I just tried configuring R to use architecture-dependent subdirs $ r_arch=x86_64 ./configure --prefix=/u/smat/konis/testdir on a Debain Squeeze box $ uname -a Linux smapc007 2.6.32-5-686 #1 SMP Sat Sep 18 02:14:45 UTC 2010 i686 GNU/Linux After building and installing, the Rconfig.h ended up in .../lib/R/include/x86_64 but R.h still includes it as #include <Rconfig.h>

Hello, I just installed R-2.15.0 on windows XP and cannot load package tcltk2 (which I just downloaded from CRAN as tcltk2_1.2-1.zip; package install reported no problems): > library(tcltk2) Carico il pacchetto richiesto: tcltk Loading Tcl/Tk interface ... done Error : .onLoad failed in loadNamespace() for 'tcltk2', details: call: system("cat /etc/issue", intern = TRUE,

A new version of the Windows batchfiles is available. CHANGES The key change is the new R.bat utility. R.bat has a new interface and extended functionality covering many of the other prior utilities. (These older utilities are no longer needed and have been removed.) Unlike R.bat which requires no configuration the new Rpathset.bat utility is configured by manually changing the Windows batch

A new version of the Windows batchfiles is available. CHANGES The key change is the new R.bat utility. R.bat has a new interface and extended functionality covering many of the other prior utilities. (These older utilities are no longer needed and have been removed.) Unlike R.bat which requires no configuration the new Rpathset.bat utility is configured by manually changing the Windows batch

Hello, Its a couple of days I am fighting with this problem, and cannot find a solution. I need to compile a DLL that is not directly used by R, but must be installed elsewhere (it is indeed part of a Tcl/Tk package). So, I want to install it in /tklibs/tkpackage/alib.dll (under Windows) in my compiled package. I do manage to compile it in /src, but cannot copy it at the right place. I

Dear all, I am forced to work in an environment without administrator rights. When using R2.13.1 on Windows 7 (64-Bit), I found that I can?t install or update any packages due to missing writing permissions. I managed to get full access to a directory on my C:\ drive now - but how do I specify that all libraries shall be installed into this directory? In Rcmd_environ I have the following