similar to: Minor feature request: Let 'R CMD co*nfig' tell me where the INCLDIR is

Hello, I was looking at the R (installed on RHEL6) shell script and saw R_HOME_DIR=/usr/lib64/R. Nowhere (and I could have got it wrong) does it read in the environment value R_HOME_DIR. I have the need to rsync the entire folder below /usr/lib64/R to another computer into another directory location. Without changing the R shell script, how can i force it read in R_HOME_DIR? Or maybe i

Hi all, It seems "samba-tool ldapcmp" does not support too much items in Samba's database. Playing for a while with DB I was never able to run ldapcmp successfully. So yesterday I installed a platform to fill piece by piece my two small DCs and to run ldapcmp. The process follows. Test platform: 2 DCs using Debian 8.1 "net install" with only system tools, up to date,

Full_Name: Philip R. Kensche Version: 2.9.1 OS: Linux Submission from: (NULL) (131.174.146.252) Use case: Run R scripts using bin/Rscript or "bin/R --no-restore --file=<script-file> --args <args>" in a heterogeneous computing grid in which it is not possible to predict the actual installation directory of the R binaries. Problem: The script bin/R and the wrapper

Hum, missed that bit. Looking at the configure script, the only way I can see it failing to look in /usr/lib/tcl8.6 is if ${LIBnn} is not "lib". Any chance it might be set to lib64? -pd > On 18 Nov 2017, at 22:32 , Rolf Turner <r.turner at auckland.ac.nz> wrote: > > > On 19/11/17 05:36, Albrecht Kauffmann wrote: > >> Did you istall the tcl- and tk-devel

This one seems to be actually working. Also rewrote doc/index.txt in case someone is interested.

On 18/11/17 18:18, Peter Langfelder wrote: > Rolf, > > looking at the configure script I believe you need to specify > > --with-tcl-config=/usr/lib/tcl8.6/tclConfig.sh > > and similarly > > --with-tk-config=<location of tkConfig.sh> > > HTH. Yes it helped. Thank you. I don't really understand why, but. I had previously (following an off-list

Full_Name: Lukasz Andrzej Bartnik Version: 2.8.1 OS: RHELS 5.2 Submission from: (NULL) (194.181.94.250) Compile R for 32 bit on a 64 bit machine: unset LD_LIBRARY_PATH unset R_LD_LIBRARY_PATH export CC="gcc -m32" export CXXFLAGS="-m32 -O2 -g" export FFLAGS="-m32 -O2 -g" export FCFLAGS="-m32 -O2 -g" export OBJCFLAGS="-m32 -O2 -g" export LIBnn=lib

Hello, It has been a while since my last R Devel build, and now I'm running into an issue I'm not sure how to isolate. After updating to the latest SVN sources, and using: ---<--------------------cut here---------------start------------------->--- tools/rsync-recommended R_PAPERSIZE=letter \ R_BATCHSAVE="--no-save --no-restore" \ R_BROWSER=xdg-open \ LIBnn=lib \

Hi Dirk, I too would need to get R-devel on my Ubuntu box (alongside an existing R installation) to check my packages, especially given the mayhem that awaits us when the new `R CMD check --as-cran` goes live. ( http://stat.ethz.ch/R-manual/R-devel/doc/html/NEWS.html ) I was wondering if the script that you posted on r-sig-debian a couple years back was still valid. More however, I'd like to

On Fri, 5 Feb 2016 06:29:46 -0600, Dirk Eddelbuettel <edd at debian.org> wrote: > On 4 February 2016 at 22:56, Sebastian P. Luque wrote: >> Hello, >> >> It has been a while since my last R Devel build, and now I'm running >> into an issue I'm not sure how to isolate. After updating to the >> latest SVN sources, and using: >> >>

NO Hi. I'm not sure if this is an R-help or R-devel problem, so I'm starting here in the hope that someone can help (and willing to go to the other list if it's more appropriate). I think I am following all of the instructions in the various manuals, but clearly I am missing something. I have an Intel EM64T Dell with 2 dual-core Xeon processors running Red Hat EL5. I would

Hi Dirk and Martyn, > That looks fine. Can you please give a reproducible example of a package > that compiles correctly on R 3.3.3 but not with R 3.4.0 or R-devel. here you go, it?s pretty much the simplest package possible that needs C++11: https://github.com/flying-sheep/cxx11test > Maybe you can share with us how you configure the build of R-devel? Sure, in the mail you quoted, I

Dear R user, I try to build R-2.8.1 on SunOS 5.9, and use following command: CC="cc -xarch=v9" CFLAGS="-xO5 -xlibmil -dalign" F77="f95 -xarch=v9" FFLAGS="-xO5 -xlibmil -dalign" CXX="CC -xarch=v9" CXXFLAGS="-xO5 -xlibmil -dalign" FC="f95 -xarch=v9" FCFLAGS="-xO5 -xlibmil

Hi, I tried to compile R with openblas on a ubuntu 12.04 machine. I have to say that I normally use the package system and that I have no experience with compiling R. I did the following: ./configure --enable-BLAS-shlib --enable-R-shlib LIBnn=lib --with-blas="-L/usr/lib/openblas-base/ -lopenblas" --enable-memory-profiling --with-x=yes go the output: R is now configured for

Does anybody know why two "-g" flags appear in the call to gcc in R CMD SHLIB Example: gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -fpic *-g* -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 *-g* -c c_file1.c -o c_object1.o Surely it need only be listed once? Alan [[alternative HTML version deleted]]

Rolf, looking at the configure script I believe you need to specify --with-tcl-config=/usr/lib/tcl8.6/tclConfig.sh and similarly --with-tk-config=<location of tkConfig.sh> HTH, Peter On Fri, Nov 17, 2017 at 8:43 PM, Rolf Turner <r.turner at auckland.ac.nz> wrote: > On 18/11/17 17:00, Erin Hodgess wrote: >> >> When I have compiled from sourced on Ubuntu, I did NOT

Full_Name: Uwe F. Mayer Version: 2.9.1 OS: SunOS myhost 5.10 Generic_120012-14 i86pc i386 i86pc Solaris Submission from: (NULL) (216.113.168.130) With the change of the NLS handling from 2.9.0 to 2.9.1 the compilation breaks, even as I do specifically not request nls. Specifics: gcc -v Using built-in specs. Target: x86_64-pc-solaris2.10 Configured with: ../../src/gcc-4.4.0/configure

Hello, I am trying to build the R-2.11.1 software for university faculty to use in research projects on a DEC/Compaq/HP AlphaServer model GS160 16CPU/64GB memory running Tru64Unix aka OSF1 version 5.1B-5. Is it known whether it is possible to build the R-2.11.1 software on the platform I am using? In my attempts to build the R-2.11.1 software, I first used the native C and Fortran 77/90/95

On 18/11/17 17:00, Erin Hodgess wrote: > When I have compiled from sourced on Ubuntu, I did NOT include the > "with-tcltk" and it worked fine.? Did you try that, please? In the past I have configured without using the "--with-tcltk" flag, and R of course built just fine. But it *did not* have tcltk capability. When I wanted that capability I had to start using the

Hi, Let me justify building R from source. While I can obtain R built for me under Ubuntu, I tend to build it from scratch as we use a NFS-shared build as well as shared R libraries for all the bioinfo staff at this company. Only one build and one set of packages to ensure uniformity across all workstations. My problem is that despite using a pretty standard build process, I am failing at the