#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:
---------------------------+------------------------------------------------
Comment(by GeorgSWeber):
Good catch!
I just finished building from scratch Sage-4.1.2.rc0, with the single
change the ecl-9.8.4 was replaced by the older ecl-9.41 spkg from
Sage-4.1.1. and had essentially the same finding as before. Starting
maxima from the build dir:
{{{
computer:/Users/Shared/sage/build/sage-4.1.2.rc0 georgweber$ maxima
;;; Loading
#P"/Users/Shared/sage/build/sage-4.1.2.rc0/local/lib/ecl-9.4.1/DEFSYSTEM.fas"
;;; Loading
#P"/Users/Shared/sage/build/sage-4.1.2.rc0/local/lib/ecl-9.4.1/cmp.fas"
;;; Loading
#P"/Users/Shared/sage/build/sage-4.1.2.rc0/local/lib/ecl-9.4.1/sysfun.lsp"
Maxima 5.19.1 http://maxima.sourceforge.net
Using Lisp ECL 9.4.1
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();
}}}
After moving, starting maxima failed silently (i.e. without error
message), but failed nevertheless. So I guessed it's not something wrong
with ecl, but with the way that maxima is built/installed. Now let's have
a look into the script $SAGE_ROOT/local/bin/maxima. Near the start, we
have:
{{{
setup_vars() {
if [ -z "$MAXIMA_VERSION" ]; then
MAXIMA_VERSION=5.19.1
fi
prefix=`unixize "/Users/Shared/sage/build/sage-4.1.2.rc0/local"`
exec_prefix=`unixize "${prefix}"`
PACKAGE=maxima
top_srcdir=`unixize
"/Users/Shared/sage/build/sage-4.1.2.rc0/spkg/build/maxima-5.19.1.p0/src"`
libdir=`unixize "${exec_prefix}/lib"`
}}}
which made me curious how this could have ever worked (it's essentially
the same for the old maxima from Sage-4.1.1). But then I saw lines 111 -
123:
{{{
setup_vars
if [ ! -d "$MAXIMA_IMAGESDIR" ]; then
# Have we been moved?
MAXIMA_PREFIX=`(cd \`dirname $0\` 1>/dev/null 2>/dev/null; dirname
\`pwd\`)`
export MAXIMA_PREFIX
unsetup_vars
setup_vars
if [ ! -d "$MAXIMA_IMAGESDIR" ]; then
echo "$0: unable to determine MAXIMA_PREFIX" 1>&2
exit 1
fi
fi
}}}
This might be a another good place to set the ECLDIR environment variable
(i.e., if it isn't already set), what do you think? (This would avoid the
introduction of a new environment variable in sage-env.)
Who's going to make the changes, and who's going to review?
(I do like the one-line change to ecl you proposed.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7186#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
