search for: libnns

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

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

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: 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

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

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

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

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

The byte pixies have rolled up R-2.14.1.tar.gz (codename "December Snowflakes") at 9:00 this morning. This is a maintenance release; see the list below for details. You can get it from http://cran.r-project.org/src/base/R-2/R-2.14.1.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team

The byte pixies have rolled up R-2.14.1.tar.gz (codename "December Snowflakes") at 9:00 this morning. This is a maintenance release; see the list below for details. You can get it from http://cran.r-project.org/src/base/R-2/R-2.14.1.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team

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: >> >>

Dirk may want to dig in here: Seems like you have a system with a /usr/lib64 dir for 64 bit libraries, but Tcl files in /usr/lib. If that is not an anomaly, it looks like we have a configure bug (conceiveably, a system might be using /usr/lib for architecture-independent files, and lib64/lib32 for binaries). It doesn't look too hard to modify configure to also check /usr/lib, but we probably

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

On Debian / Ubuntu / ... we have [1] edd at ron:~> R CMD config --cppflags -I/usr/share/R/include edd at ron:~> but I seem to have no way to learn 'just' the /usr/share/R/include part from R CMD config. It would be nice if something like R CMD config R_INCL_DIR could be added as we do have 'LIBnn'. Obviously, this is nothing we need now before 2.8.0. But if it

This refactoring takes the nbdkit-specific code from the ‘-it vddk’ mode and puts it into a separate module. The idea is to reuse this module (in future commits) to support ssh, curl and rate limiting. This refactoring is not quite neutral because it moves some of the prechecking into the Nbdkit.create function. This means it will happen a little bit later in the cycle (in input#source instead

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

On 12.11.2016 18:38, Dirk Eddelbuettel wrote: > On 12 November 2016 at 07:59, Dirk Eddelbuettel wrote: > | > | On 12 November 2016 at 14:23, Kirill M?ller wrote: > | | Thanks. I have now CXX = g++ -std=c++98 in my /etc/R/Makeconf, it's > | | picked up properly. I can only assume that the last -std= option wins if > | | more than one are given on the same command line [1].

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