Hmmm, maybe I was lucky. The trac fix works for me too.
Should sage have a few/several more "SAGE_ORIG_XXXX" vars for
sage-native-execute
to restore?
On Tuesday, October 22, 2013 2:05:52 AM UTC-4, Nils Bruin wrote:
>
>
>
> On Monday, October 21, 2013 10:39:03 PM UTC-7, rickhg12hs wrote:
>>
>> Since Sage depends on the host system's runsnake command, how about
>> letting it have its LD_LIBRARY_PATH to run? Changing one line in
>> .../sage/misc/dev_tools.py allows it to work on my system.
>>
>> Last line of current runsnake definition:
>>
>> os.system("/usr/bin/python -E `which runsnake` %s &"%tmpfile)
>>
>> See
>
> http://trac.sagemath.org/ticket/14414
>
> If you can get away with resetting only LD_LIBRARY_PATH, congratulations,
> but there are a few more variables that are problematic when you try to run
> native python programs in the environment that sage sets up.
>
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/groups/opt_out.
