Christopher Barker wrote: >> *** PIL CORE support not installed > > That sure doesn't look good! > >> *** TKINTER support not installed >> --- JPEG support ok >> --- ZLIB (PNG/ZIP) support ok >> *** FREETYPE2 support not installed >> *** LITTLECMS support not installed > > neither do those.
Ha! I haven't had a look at selftest.py before. That script requires an inplace build which I didn't do. Instead, I was pointing PYTHONPATH inside the build directory and thought it would then pick the modules up from there, but the test script imports from "PIL" which is not available in the build directory, so it failed to import any of the so libs. After doing an inplace build, the test script runs fine. But when I link against the static lib, the test script only runs fine because it imports the tk module before the freetype one. Whereas when I just import _imagingft, I get this: >>> import PIL._imagingft Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: dlopen(PIL/_imagingft.so, 2): Symbol not found: _FSOpenResFile Referenced from: PIL/_imagingft.so Expected in: dynamic lookup This error does not occur if _imagingtk is imported first. So it looks like we would have to link against some system library when building _imagingft. By the way, _imaging.so still depends on /usr/lib/libz.1.dylib, but I suppose as this is a library that ships with OSX, this should be available on all systems and so it should be fine. Is this correct? - Matthias - _______________________________________________ Image-SIG maillist - Image-SIG@python.org http://mail.python.org/mailman/listinfo/image-sig
