#7186: maxima update #6699 introduced hard-coded paths, unable to start maxima
---------------------------+------------------------------------------------
Reporter: GeorgSWeber | Owner: tbd
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.1.2
Component: build | Keywords:
Work_issues: | Author:
Reviewer: | Merged:
---------------------------+------------------------------------------------
Just take a newly built Sage-4.1.2.alpha4, say, containing the newly
introduced maxima 5.19.1 / ecl 9.8.4 (Sage-4.1.1 had older versions of
maxima/ecl). In the SAGE_ROOT directory type
{{{
(build_path)$ ./sage -sh
(build_path)$ sage
----------------------------------------------------------------------
| Sage Version 4.1.2.alpha4, Release Date: 2009-09-27 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
**********************************************************************
* *
* Warning: this is a prerelease version, and it may be unstable. *
* *
**********************************************************************
sage: exit
(build_path)$ maxima
;;; Loading
#P"/Users/Shared/sage/sage-4.1.2.alpha4/local/lib/ecl-9.8.4/DEFSYSTEM.fas"
;;; Loading
#P"/Users/Shared/sage/sage-4.1.2.alpha4/local/lib/ecl-9.8.4/cmp.fas"
;;; Loading
#P"/Users/Shared/sage/sage-4.1.2.alpha4/local/lib/ecl-9.8.4/sysfun.lsp"
Maxima 5.19.1 http://maxima.sourceforge.net
Using Lisp ECL 9.8.4
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) quit();
}}}
and you'll see a slightly different output, since obviously a hardcoded
path to ecl is displayed. Now move the entire Sage build to some other
directory. Type the above again, you'll get
{{{
(other_path)$ ./sage -sh
(other_path)$ sage
----------------------------------------------------------------------
| Sage Version 4.1.2.alpha4, Release Date: 2009-09-27 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
**********************************************************************
* *
* Warning: this is a prerelease version, and it may be unstable. *
* *
**********************************************************************
The Sage install tree may have moved.
Regenerating Python.pyo and .pyc files that hardcode the install PATH
(please wait at most a few minutes)...
Do not interrupt this.
Loading Sage library. Current Mercurial branch is: test
sage: exit
Exiting SAGE (CPU time 0m0.14s, Wall time 0m7.62s).
Exiting spawned Gap process.
(other_path)$ maxima
Internal or unrecoverable error in:
Cannot find ECL's directory
[2: No such file or directory]
Abort trap
(other_path)$
}}}
and inside this "moved" Sage, any calls to functionalities involving
calling maxima now fail thus:
{{{
sage: f = x^2
sage: f.integrate(x)
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (2, 0))
---------------------------------------------------------------------------
TypeError Traceback (most recent call
last)
...
TypeError: Unable to start maxima
}}}
This means, among other things, that it will be impossible to create Sage
binaries, that work --- unless they're installed in *precisely* the path
they were built in!
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7186>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
