Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#4216 closed defect (fixed)

[with patch, positive review] use sage-native-execute to run 'convert' in animate.py

Reported by: jhpalmieri Owned by: somebody
Priority: minor Milestone: sage-3.1.3
Component: graphics Keywords: animate, convert, sage-native-execute
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

On my Mac, I was getting this error with the animate command:

sage: a = animate([sin(x + float(k)) for k in srange(0,2*pi,0.3)],
xmin=0, xmax=2*pi, figsize=[2,1])
sage: a.show()
dyld: Symbol not found: __cg_png_create_info_struct
  Referenced from:
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/
Frameworks/ImageIO.framework/Versions/A/ImageIO
  Expected in: /Applications/sage/local/lib//libPng.dylib

sh: line 1: 75999 Trace/BPT trap          convert -delay 20 -loop 0
*.png
"/Users/palmieri/.sage/sage_notebook/worksheets/admin/46/cells/37/
sage0.gif" 

In the discussion <http://groups.google.com/group/sage-support/browse_frm/thread/526afa1bcc4b7ad5>, it was suggested that 'sage-native-execute' should be used to run the 'convert' command, and this seems to fix the problems.

Please check this on several different platforms.

Attachments (1)

4216.patch (840 bytes) - added by jhpalmieri 13 years ago.

Download all attachments as: .zip

Change History (5)

Changed 13 years ago by jhpalmieri

comment:1 Changed 13 years ago by jhpalmieri

  • Milestone changed from sage-3.2 to sage-3.1.3

comment:2 Changed 13 years ago by mabshoff

  • Summary changed from [with patch, needs review] use sage-native-execute to run 'convert' in animate.py to [with patch, positive review] use sage-native-execute to run 'convert' in animate.py

Positive review.

Cheers,

Michael

comment:3 Changed 13 years ago by mabshoff

  • Resolution set to fixed
  • Status changed from new to closed

Merged in Sage 3.1.3.alpha2

comment:4 Changed 13 years ago by mhansen

These are related: #3012 and #767

Note: See TracTickets for help on using tickets.