On 09/23/10 04:29 PM, John H Palmieri wrote:
Notice two of the last last 3 lines above say
Making Sage/Python scripts relocatable...
python: No such file or directory
This is from the script sage-spkg:
echo "Making Sage/Python scripts relocatable..."
cd "$SAGE_LOCAL"/bin
./sage-make_relative
Then sage-make_relative is a python script.
Maybe this part of the script should test for python's existence
first, and if it's there, run it. Or test for the existence of both
local/bin/python/... and python?
--
John
Looking at the comments on the end, it makes no difference if this works or not
before Python is built. I think testing for $SAGE_LOCAL/bin/python is probably
the best solution. I would not test for a system python, in case there's a
broken installation of Python, in which case it's anyones guess what will
happen. This error message is apparently harmless, but it's a bit dumb to have
confusing error messages.
===========================================================
echo "Making Sage/Python scripts relocatable..."
cd "$SAGE_LOCAL"/bin
./sage-make_relative
echo "Finished installing $PKG_NAME.spkg"
# It's OK if the above fails -- in fact it will until Python
# itself gets installed. That's fine.
exit 0
==========================================================
I think just adding an
if [ -f "$SAGE_LOCAL/bin/pthon" ]
around the last few lines would avoid the error message.
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
