On Apr 1, 5:13 pm, "John P. Burkett" <[EMAIL PROTECTED]> wrote:

Hi John

> Trying to upgrade to SAGE 2.11 on a Dell with an
> i686 Intel Pentium D chip and a CPU running at 2.80 GH under Gentoo
> Linux,  I (as root) did "sage -upgrade".  Near the end of the process, a
> message appeared saying that the clisp executable was not installed. The
> message also stated the the following:
> "If you already have clisp, you can type touch spkg/installed/clisp-2.38
> (or whatever the current version is) from SAGE_ROOT, and continue the
> install." I tried doing "touch spkg/installed/clisp-2.41" and repeating
> "sage -upgrade" but the problem persisted.  The message that appeared on
> this second attempt, similar or identical to the first message, reads in
> part as follows:
> "/usr/bin/install: cannot stat `clisp.pdf': No such file or directory
> make[1]: *** [install-man] Error 1
> make[1]: Leaving directory
> "/usr/local/sage-2.8.2-debian32-i686-Linux/spkg/build/clisp-2.41.p13/src/src'
> Something went wrong -- the clisp executable was not installed.
> If you already have clisp, you can type touch spkg/installed/clisp-2.38
> (or whatever the current version is) from SAGE_ROOT, and continue the
> install.  This tells SAGE that you already have clisp-2.38 installed.
> Clisp is only used by the Maxima component of SAGE.
> real    3m56.837s
> user    3m25.190s
> sys     0m30.153s
> sage: An error occurred while installing clisp-2.41.p13"

Please gzip up install.log and post a link here so that I can take a
look. My magic power of deduction is in the shop, so I need to take a
look at the logs ;)

> Near the end of my lengthy
> /usr/local/sage-2.8.2-debian32-i686-Linux/install.log
> the following, possibly relevant, lines appear:
> "Setting RHOMES to  ['/usr/lib/R']
> Traceback (most recent call last):
>    File "setup.py", line 106, in <module>
>      RVERSION = rpy_tools.get_R_VERSION(RHOME, force_exec=True)
>    File
> "/usr/local/sage-2.8.2-debian32-i686-Linux/spkg/build/rpy-1.0.1.p1/src/rpy_tools.py",
> line 99, in get_R_VERSION
>      " `%s'.\n" % rexec )
> RuntimeError: Couldn't execute the R interpreter `/usr/lib/R/bin/R'.
> Error building RPY -- Python interface to R.
> real    0m0.221s
> user    0m0.066s
> sys     0m0.018s
> sage: An error occurred while installing rpy-1.0.1.p1"
>
> The file /usr/lib/R/bin/R exists.  When I type "R", R starts.  I don't
> why the system "couldn't execute the R interpreter."
>
> Any help in resolving this problem would be greatly appreciated.

R isn't easily relocatable. I did fix the issue on OSX since I was
under the impression that it works on Linux. I can fix it in an analog
way on Linux.

> Best regards,
> John

Cheers,

Michael

> --
> John P. Burkett
> Department of Environmental and Natural Resource Economics
> and Department of Economics
> University of Rhode Island
> Kingston, RI 02881-0808
> USA
>
> phone (401) 874-9195
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to