Skip to content

help-links.sh not found by help.start() -- do I need to recompile?

6 messages · Peter Dalgaard, Marc Schwartz, Ivailo

Ivailo
# 
No, I haven't used "make install" because I prefer to run R from within 
the build location.
AFAIK, the approach of running R from within the build location is fully 
valid as it is noted at the end of section "2.1 Simple compilation", 
just above the cited one:

"... Note: you do not need to install R: you can run it from where it 
was built."

All the best,
Ivailo
Peter Dalgaard
#
Ivailo Stoyanov wrote:
Yes, but then it is not "actually installed".
You can, but note that it doesn't say that you can move the build 
location afterwards, and in fact, you can not, because of the 
non-relative pathnames.
Marc Schwartz
#
On Thu, 2006-12-07 at 20:15 +0200, Ivailo Stoyanov wrote:
A key piece of information not in your original post was that you were
not "installing" R, but wanted to run it from whence it was built...and
then moved it and were attempting to run it from a new location.

You will need to change $R_HOME, which defines the primary home
directory for the currently running R session.  This is defined in the
main R startup script, which will be in the 'bin' sub-directory for your
R tree.

I have not validated this that will do it, but short of re-building R in
the new location, this should work I think. Many of the environmental
vars are hard coded during the build process and then modified during a
"make install" based upon build time configuration options. If you want
to install R in a non-default location, I would suggest considering
modifying the ./configure options and then building to suit your needs.

HTH,

Marc
Ivailo
#
Peter Dalgaard wrote:
[snip]
[snip]
Actually, I have used R for a long time without any (apparent) problems 
being "installed" this way. I just changed the mentioned variables 
manually, and everything was running just fine -- until I needed to 
check the HTML help recently. Therefore I thought that I've missed to 
fix some config-file in an analogous maner to solve the problem with the 
script that wasn't found by the system.

I assume that I have to recompile (something that I was hoping to avoid 
due to the rather decent system I use currently) to get this issue 
fixed. Am I right?
Ivailo
#
Marc Schwartz wrote:
OK, I'll check the ./configure options passed through the build script I 
used last time.

Thanks to all helpers so far,
Ivailo
Ivailo
# 
Thanks to the valuable hints posted, I managed to track down the source 
of the problem -- a copy of the *uncorrected* /usr/lib/R/bin/R script 
was left over in /usr/bin.

Thank you again for the patience!

Greets,
Ivailo