On Sep 14, 2008, at 9:48 PM, mabshoff wrote:
> On Sep 14, 7:46 pm, Justin Walker <[EMAIL PROTECTED]> wrote:
>> On Sep 14, 2008, at 9:28 PM, Justin Walker wrote:
>
> <SNIP>
>
>> Inspired by a post by William, I ran the "tut.tex" test, with the
>> verbose switch.
>>
>> If anyone's interested, the log file is in
>>     <http://sage.math.washington.edu:~justin/logs/tut-080914.log>
>>
>> The log ends here:
>>
>> File "/SandBox/Justin/sb/sage-3.1.2.rc3/tmp/.doctest_tut.py", line
>> 550, in __main__.example_33
>> Failed example:
>>      show(P)###line 945:_sage_    : show(P)
>> Exception raised:
>>      Traceback (most recent call last):
>>        File "/SandBox/Justin/sb/sage-3.1.2.rc3/local/lib/python2.5/
>> doctest.py", line 1228, in __run
>>          compileflags, 1) in test.globs
>>        File "<doctest __main__.example_33[4]>", line 1, in <module>
>>          show(P)###line 945:_sage_    : show(P)
>>        File "/SandBox/Justin/sb/sage-3.1.2.rc3/local/lib/python2.5/
>> site-packages/sage/misc/functional.py", line 900, in show
>>          return x.show(*args, **kwds)
>>        File "/SandBox/Justin/sb/sage-3.1.2.rc3/local/lib/python2.5/
>> site-packages/
>>
>> and 'sage' goes into mad whirl, with no output, but a lot of CPU  
>> usage.
>
> Ok, this is not Maxima, but very likely Sage picking up a libpng.dylib
> from eithe Fink or MacPorts. Moving those two out of the way (or
> DYLD_LIBRAY_PATH) should potentially fix this issue.

I have libpng.dylib in /opt and /usr/X11.  Doesn't Sage protect itself  
against these interlopers?

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
If it weren't for carbon-14, I wouldn't date at all.
-----------



--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to