[Pythonmac-SIG] compiling PIL on OSX10.5
vip at avatar.com.au
Thu Feb 28 15:41:26 CET 2008
Hey Ronald - I recon that way madness lies!
I sent the last post and then realised I could run both a new and old
so I downloaded and have begun - wow - talk about speed!
btw it's quite hard to work out where exactly to get the .dmg
from - sometimes MacPython is called python (under a mac heading) etc
(went around the loop a couple of times and eventually downloaded
which instantiates as
> Python 2.5.2 (r252:60911, Feb 22 2008, 07:57:53)
> [GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> Executable: /Library/Frameworks/Python.framework/Versions/2.5/
Is that the right one?
Anyway PIL compiles and loads, so,sorry to bother you about this -
Sometimes it's better to bite the bullet!
On 28/02/2008, at 11:03 PM, Ronald Oussoren wrote:
> On 28 Feb, 2008, at 12:49, DavidW wrote:
>> Hi Ronald, Thanks for replying.
>> On 28/02/2008, at 9:18 PM, Ronald Oussoren wrote:
>>> Which version of python are you using? The Python.org installer
>>> builds extensions using the 10.4 SDK to ensure that extensions will
>>> actually run on that platform.
>> Python 2.4.3 (#1, Mar 30 2006, 11:02:16)
>> [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin
>>> BTW. What I don't undestand is why building PIL tries to link
>>> Do you have a libcrypto dylib in /usr/local/lib? If so, what is the
>>> output of the file command on that? (file /usr/local/lib/
>>> libcrypto*). It seems that the libcrypto that's linked into the
>>> extension is PPC-only, while distutils tries to build a 32-bit
>>> universal binary.
>> you guessed it!
>> Macintosh:SDKs drw$ file /usr/local/lib/libcr*
>> /usr/local/lib/libcrypto.0.9.7.dylib: Mach-O dynamically linked
>> library ppc
>> Now I'm wondering what to do. This is an intel macbook. upgrade from
>> OSX 10.4.11 to 10.5 was ?ok? but things got stuffed up when trying to
>> implement the 10.5.1 upgrade. Recommendation?
> I don't know what installed libcrypto in /usr/local/lib and hence
> don't know if it is save to remove.
> You could move it (or all of /usr/local) aside while building pil
> and restore it afterwards.
> I'd try to find out what installed /usr/local/lib/libcrypto* and
> reinstall it as a universal or x86 library.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pythonmac-SIG