On Sun, Jul 20, 2008 at 5:45 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
>> There must be a way to get this fixed, so that Sage can be used as a
>> library and it can use it's own compiled libs, but it will not force
>> the rest of the system to use them. Or there isn't?
>
> There pretty much isn't.
>
> However you can maybe do:
>
> sage: os.system('unset LD_LIBRARY_PATH; gedit')
>
> Alternatively, we have a script sage-native-execute
>
> sage-native-execute gedit
>
> that is in SAGE_ROOT/local/bin/
> that Sage itself uses whenever sage library code calls
> system-wide binaries.
This script just sets the LD_LIBRARY_PATH to "" (in my case). Indeed, the
sage: os.system('unset LD_LIBRARY_PATH; gedit')
works, but because the PATHs are set to use sage python, other
programs will not run anyway:
sage: os.system('unset LD_LIBRARY_PATH; mayavi2')
Traceback (most recent call last):
File "/usr/bin/mayavi2", line 3, in <module>
from enthought.mayavi.scripts import mayavi2
ImportError: No module named mayavi.scripts
256
Hm, Sage just needs LD_LIBRARY_PATH and PATH set to something, while
the rest of the system to something else.
Well, PATHs could be fixed somehow. The problem is LD_LIBRARY_PATH --
but I think there is something like chrpath, that could fix the
problem.
E.g. maybe it's possible to write a script that sets this in Sage
automatically on the first run. I just believe there must be a way to
get this fixed.
The other option is to use Sage debian packages.
> There is now a patch up at
> http://trac.sagemath.org/sage_trac/ticket/3685
> that fixes the above-mentioned problem.
Thanks for fixing this!
Ondrej
--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
