similar to: Sys.which() caching path to `which`

Harmen, thanks for the additional details, it wasn't exactly clear what this is about. Ivan's post didn't mention that the issue here is the caching, not the path replacement which you are apparently already doing, now it makes more sense. I still think it is dangerous as you have no way of knowing who else is caching values at installation time since there is no reason to assume

I saw an email about 8.0.1 being not quite out, and planning for 9.0.0. When is 8.0.1 supposed to come out? I installed llvm at develop on x86 on March 30, and its clang says it is version 9.0.0 (trunk 357348). I tried to do another spack install llvm at develop, but it said that I already had it installed. Does that mean there were no changes since March 30, or does spack not look for any

Thank you. > On Jul 3, 2019, at 4:04 AM, Justin Clift <justin at postgresql.org> wrote: > > On 2019-07-01 00:22, Marty Itzkowitz via llvm-dev wrote: >> I also tried spack install llvm at develop on a POWER9 (ppc641e) >> machine, but I can not find a compiler that >> will compile it. gcc 4.8.5 is reported as too old, and gcc 7.3.0 and >> 8.1.0 both fail in

Dear everyone, Your code is slow and you are interested in performance optimization for scientific software? Figuring out where’s the bottlenecks guided by performance evaluation tools. If you are interested in porting your code to a HPC hardware platform and architecture, than OpenACC as a user-driven directive-based performance-portable parallel programming model might be a solution. What are

Hi, It may be useful for testing purpose to know if a generated password hash correspond to a given clear password. This can be useful to check if a hash generated by another program can be verified by Dovecot without any errors. This patch adds the ability the verify a password hash using `doveadm pw` via the `-V` option. ??? $ doveadm pw -s SSHA.hex ??? Enter new password: ??? Retype new

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

Without seeing more details it's impossible to tell, but it might have been me. https://github.com/llvm/llvm-project/commit/6102310d814ad73eab60a88b21dd70874f7a056f#diff-0f9a49c4e31c311a0010e126cd785f08 changed PHI node equality check, but there were some users that implicitly depended on the old definition of the PHI equality, and didn't verify their implicit assumptions with reality,

Hello, In installation/R/bin/R i notice 1. R_HOME_DIR is hard coded e.g. R_HOME_DIR=/usr/local/lib64/R 2. It ignores R_HOME_DIR echo "WARNING: ignoring environment value of R_HOME" 3. R_SHARE_DIR, R_INCLUDE_DIR and R_DOC_DIR are also hard coded. Is there a reason why these settings do not read the values from the environment variables of the same name (assuming they exist) and

I have just installed the version of R for Linux Enterprise Server AS. When R is launched, I receive the following error message: R: error while loading shared libraries: libg2c.so.o cannot open shared object file: no such file or directory I have added the path to the library above to the /usr/etc/ld.so.conf file and then run ldconfig -v. The listing then shows that the libg2c.so.o is

R-help -- I built R-2.2.1 in my own directory on a sun (solaris). Now I would like the sysadmin to move the contents to /usr/local/lib and place the binary in /usr/local/bin. No problem. However, the RHOME variable defaults to the directory from which R was built so it is not usable by anyone but me or ROOT. I would like to avoid building this again if possible. Any ideas? Thanks, Dan

I am not sure if anyone else has run into this, but i did today when setting upo a samba server. http://lists.gobolinux.org/pipermail/gobolinux-users/2007-February/004413.html In an nutshell you get an error like: "usermod: invalid numeric argument", or the user groups are never assigned, etc. So I have been managing manually. I get the exact same symptoms, etc (but doing things like

[This is not a bug report, just a suggestion.] With complex packages, it is often useful to maintain multiple versions installed, for bug checking, and performance comparisons, and for developers, for a development history (e.g., I have about 30 versions of ghostscript, whose development I contribute to, and I have on several occasions run tests files on with each them to find out when a change

I am running R 1.2.1 under Mandrake Linux 7.2 (installed from RPM) and I installed a few packages using install.packages() . Now, I am trying to upgrade these packages using update.packages() but I believe I am running into some kind of error. See below. Any tips will be greatly welcome. Thanks in advance. Francisco PS: update.packages() only tries to update wle from version 0.3 to 0.4, gives

On Thu, 11 Jan 2024 09:30:55 +1300 Simon Urbanek <simon.urbanek at R-project.org> wrote: > That said, WHICH is a mess - it may make sense to switch to the > command -v built-in which is part of POSIX (where available - which > is almost everywhere today) which would not require an external tool This is a bit tricky to implement. I've prepared the patch at the end of this

Dear all, I am sorry in advance because probably my question was already discussed. I have installed an R version R-1.3.1 on Linux RedHat 6.2. As I want to install R-1.5.0, I have first followed a suggestion of Peter Dalgaard (mail in FAQ) in order to keep the version R-1.3.1 by renaming /usr/local/lib/R and /usr/local/bin/R (/usr/local/lib/R-1.3.1 and /usr/local/bin/R-1.3.1 )and then set

I am troubled by what appears to be a glitch in the current distribution, or in its installation on our system. I've traced it, and found a work- around. Is this normal? Is there a cleaner solution? The problem: During a package installation, the warning message "WARNING: ignoring environment value of R_HOME" from line 31 of <R_HOME>/bin/R is accidentally spliced into the

On Wed, Sep 21, 2016 at 7:39 PM, Tom Callaway <tcallawa at redhat.com> wrote: > > On 09/16/2016 10:28 AM, Jeroen Ooms wrote: > > Where are the R docs located on EL6? It seems neither R.home("doc") > > nor Sys.getenv("R_DOC_DIR") exists? > > /usr/share/doc/R-3.3.1 > Can we set this in R_DOC_DIR accordingly so that it can be programmatically

I'm trying to install packages in Gentoo Linux using install.packages(). The packages download fine, but when it comes to installation, I get this message: WARNING: ignoring environment value of R_HOME /var/tmp/portage/R-1.5.1/image//usr/lib/R/bin/Rcmd: /var/tmp/portage/R-1.5.1/image//usr/lib/R/bin/Rcmd: No such file or directory I have the R_HOME set to the correct value (/usr/lib/R), but I

I'm trying to run multiple simulations using R on a cluster of pentiums running Solaris X86 by batching the R routines and simultaneously farming them out to the cluster nodes. This works fine on some of the machines, but on others the directory structure is mapped differently, so that when I try to run R, it can't be found, I can get around this by running /net/mp1/space/local/bin/R

Hi helpteam, may you send me the exact syntax for getting the estimated degrees of freedom for a gam? I tried to do it by name <- edf(gam_name) but this didn't work. Thanks a lot, greetings from Munich, Thomas Nittner -- Thomas Nittner Tel: ++49 89 2180 3197 Akademiestra?e 1 Fax: ++49 89 2180 5042 D - 80799 M?nchen http://www.stat.uni-muenchen.de