Re: Unable to import _imaging
Esben Bugge <[email protected]>
| Newsgroups | gmane.comp.python.image |
|---|---|
| Message-ID | <[email protected]> |
otool -L _imaging.so
gave me
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/PIL/_imaging.so
(architecture ppc):
/usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version
315.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
125.2.0)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/PIL/_imaging.so
(architecture i386):
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
125.2.0)
That doesn't mention anything about jpeg...?
Anyway, I used the binaries and now it seems to work just fine :)
On 8 November 2010 18:21, Christopher Barker <[email protected]> wrote:
> On 11/6/10 2:30 PM, Esben Bugge wrote:
>
>> I am trying to install PIL on Mac OS.X 10.6 for the purpose of using
>> Satchmo. After installation I tried
>>
>
> getting PIL built on OS-X is a bit of a pain. If you want to run it just on
> your system, the easiest way is to get the dependencies from macports, and
> then build PIL with those.
>
> A note: OS-X generally (always?) hard-codes the path to dependent libs when
> linking. so you can do:
>
> otool -L _imaging.so
>
> and you should see what it's linked against.
>
> But far easier is to install a binary. Russell Owen has built some, that
> you can find here:
>
> <http://www.astro.washington.edu/users/rowen/python/>
>
> Fredrik: please put these up the PIL site!
>
> -Chris
>
>
>
>
> --
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R (206) 526-6959 voice
> 7600 Sand Point Way NE (206) 526-6329 fax
> Seattle, WA 98115 (206) 526-6317 main reception
>
> [email protected]
>
_______________________________________________
Image-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/image-sig