As a further update for those interested, the above method works in
both binary windows (vmware) and linux versions. However, on Linux, an
easier method is to install sage from the binary, and then reinstall R
from source. This incidentally enables png, jpeg and X11 in R if the
required development
On Aug 4, 4:44 am, ancienthart wrote:
> Hi kcrisman,
> Yes, this was the latest binary release of sage, on an ubuntu
> machine,
> sage-4.5-linux-64bit-ubuntu_10.04_lts-x86_64-Linux.tar.lzma
>
> I suspect that the only thing I need to change is the R_INCLUDE_HOME=
> lines, but when I try to get s
Hi kcrisman,
Yes, this was the latest binary release of sage, on an ubuntu
machine,
sage-4.5-linux-64bit-ubuntu_10.04_lts-x86_64-Linux.tar.lzma
I suspect that the only thing I need to change is the R_INCLUDE_HOME=
lines, but when I try to get something working, I don't like to leave
anything to ch
Dear Joal,
Was this a downloaded binary? The variable '/scratch/...' seems to
indicate this is the case. This is usually not a problem on a 'home-
built' one - I've installed lots of R packages using
sage: r.install_packages()
I'm opening a Trac ticket for this, but unfortunately don't know
en
*sigh*
And I bludgeon the solution out the very next night.
Here is how I got the optional package automap to install into a
binary sage R.
Go into the sage directory and edit the following files:
local/bin/R and local/lib/R/bin/R
and change all the hard-set user variables "/scratch/" to the t
