On OSX, the path_helper command is always executed when starting a new
shell. Unfortunately, the path_helper command prepends standard system
values to the PATH variable, which means that the Sage-specific values
come at the end of the PATH variable. This causes all sorts of breakage
when trying to use sage -sh to do something.
I'm on OSX 10.6.6. Can people try the following commands:
bash-3.2$ sage -sh
Detected SAGE64 flag
Building Sage on OS X in 64-bit mode
Starting subshell with Sage environment variables set.
Be sure to exit when you are done and do not do anything
with other copies of Sage!
Bypassing shell configuration files ...
SAGE_ROOT=/Users/grout/sage
(sage subshell) tiny:~/sage/local/bin grout$ echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/usr/texbin:/usr/X11/bin:/Users/grout/sage/local/Frameworks/Python.framework/Versions/2.5/bin:/Users/grout/sage:/Users/grout/sage/local/bin:.
In your sage -sh $PATH variable, do the sage directories come at the end
or the beginning? I'm particularly interested in people with OSX 10.6.6.
The problem might be a bug in path_helper in OSX (unless something is
messed up with my configuration). The manpage for path_helper says that
it appends its values to $PATH, but this example shows it clearly
*prepends* its new paths to the $PATH variable:
bash-3.2$ PATH='.';export PATH
bash-3.2$ /usr/libexec/path_helper -s
PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/usr/texbin:/usr/X11/bin:.";
export PATH;
Thanks,
Jason
--
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
