> > 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. >
Maybe yes, maybe no, the PIL setup.py intentionally probes for external libraries that do not come with Sage. These may be installed in different locations on different computers, so what you see might be just OK. The only "good" solution would be to officially incorporate some libjpeg.spkg and libtiff.spkg in Sage, or to cripple PIL to never probe for those (which is necessary if you build binary distribitions, that's what the env var from my former message is for). The current situation is somewhat a compromise. Not that the PIL setup.py couldn't be streamlined a bit further, but there's more important work to do. Cheers, Georg -- 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
