On 5/6/07, cwitty <[EMAIL PROTECTED]> wrote: > > I've posted sage-2.5.alpha3 here: > > > > http://sage.math.washington.edu/home/was/sage2.5/ > > > > Feedback is welcome. > > On my machine running Debian testing, plotting-related tests fail with > messages like: > > libpng error: Incompatible libpng version in application and library > > A mysterious error (perphaps a memory error?) occured, which may have > crashed doctest. > > I think I understand why this is happening. Debian testing includes a > new version of libpng (version 1.4, package names libpng14-1 and > libpng14-dev). When matplotlib is compiled (in particular, the file > _ns_image.cpp, which produces _ns_image.so), it uses a -I flag to > include the png.h header file from SAGE's local version of libpng > (version 1.2.16). However, when the resulting object file is linked, > to actually produce _ns_image.so, it has no special -L flags, so it > ends up linked against Debian's version 1.4 libpng. At runtime, > libpng 1.4 notices that the application was compiled against the > version 1.2.16 png.h header file; this is a fatal error, and exits > SAGE. > > The fix is to change the matplotlib spkg-install, so that the > _ns_image.so link command has the right -L flag to link against SAGE's > libpng. (I don't know enough about the Python compile system to do > this myself.)
Many thanks for tracking this down!! I greatly appreciate it. -- William --~--~---------~--~----~------------~-------~--~----~ 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
