RetroSearch Browse

Fri Oct 31 19:06:32 EST 2003 · http://mail.python.org/pipermail/pythonmac-sig/2003-October/009241.html

Thanks to some kind folks on the MacPython ichat channel last night,
we tracked the problem down further.  The build process is for some
reason creating an _imaging.so file with the following names in it:

  % otool -Lv /Library/Python/2.3/PIL/_imaging.so 
  /Library/Python/2.3/PIL/_imaging.so:
	Python.framework/Versions/2.3/Python (compatibility version 2.3.0, current version 2.3.0)
	time stamp 1067389093 Tue Oct 28 16:58:13 2003
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.0.0)
	time stamp 1064385339 Tue Sep 23 23:35:39 2003
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.0.0)
	time stamp 1064354548 Tue Sep 23 15:02:28 2003
  %

For some reason, the first line "Python.framework..." is wrong (don't
ask me how I know -- I was told).  By applying another magic
incantation,

  % install_name_tool -change Python.framework/Versions/2.3/Python \
    /System/Library/Frameworks/Python.framework/Versions/2.3/Python

things get fixed, and the Image module loads properly.

It seems to me that this means there's a bug somewhere in gcc 3.3 as
deployed on MacOS 10.3.  Something's putting that bad name in there.

Bill

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/pythonmac-sig/2003-October/009241.html below:

PIL 1.1.4 breaks Python 2.3 on Mac OS X 10.3 Panther