On Feb 20, 2:09 pm, "Georg S. Weber" <georgswe...@googlemail.com> wrote: > Hi John, > > AFAIK, the "_import" module is built by the PIL spkg. Try reinstalling > it, eventually you have to issue "export SAGE_BINARY_BUILD=yes" > before, in order to make PIL build sanely (I have to do that every > time on my production machine).
I tried reinstalling it, running this export command first, and that seems to have worked. I noticed one difference on the two machines: on the one where I don't have the failure, it says --- using frameworks at /System/Library/Frameworks and on the other one, it says --- using frameworks at /Library/Frameworks I think there may be some bad things in the second directory, from when I tried to build python or tcl or tk, and maybe those are interfering somehow. Our spkg should try to guard against this, somehow. > I have no idea whether this is related > to the segfaults you see after updating, however. Were these installs > older than the MACOSX_DEPLOYMENT_TARGET patch (I don't remember the > ticket number)? No, this was upgraded from 4.3.3.alpha0, which itself was built from scratch. -- John -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
