Re: [Pyobjc-dev] pyobjc 2.3 install fails

[Ronald O. <ron...@ma...>]

On 9 Dec, 2010, at 16:43, Mark Sienkiewicz wrote:

> 
>>> error: Could not find required distribution pyobjc-core
>>> 
>>> As far as I can tell, some part of it must be missing from pypi.  Any ideas?
>> That's odd, pyobjc-core is on pypi and should work just fine.
>> Could you try "easy_install pyobjc-core==2.3" followed running "python setup.py install" for pyobjc itself again?
> 
> 
> I did this:
> 
> setenv PYTHONPATH     /Users/sienkiew/py/lib/python2.7/site-packages
> easy_install --prefix ~/py pyobjc-core==2.3
> 
> It installed something that involved compiling a lot of C code.  During the install, there were a few things that look broken, though:
> 
> 
> libtool: link: ar cru .libs/libxml2.a  SAX.o entities.o encoding.o error.o parserInternals.o parser.o tree.o hash.o list.o xmlIO.o xmlmemory o uri.o valid.o xlink.o HTMLparser.o HTMLtree.o debugXML.o xpath.o xpointer.o xinclude.o nanohttp.o nanoftp.o DOCBparser.o catalog.o globals o threads.o c14n.o xmlstring.o xmlregexp.o xmlschemas.o xmlschemastypes.o xmlunicode.o xmlreader.o relaxng.o dict.o SAX2.o xmlwriter.o legac .o chvalid.o pattern.o xmlsave.o xmlmodule.o schematron.o
> ranlib: file: .libs/libxml2.a(SAX.o) has no symbols
> ranlib: file: .libs/libxml2.a(xlink.o) has no symbols
> ranlib: file: .libs/libxml2.a(HTMLparser.o) has no symbols
> ranlib: file: .libs/libxml2.a(HTMLtree.o) has no symbols
> ... repeats for about 20 more files ...

This is harmless, due to the way pyobjc compiles a 3th party library we end up with some empty C object files.
> 
> And later:
> 
> Modules/objc/test/properties.m:24: warning: Mac OS X version 10.5 or later is needed for use of property
> Modules/objc/test/properties.m:25: warning: Mac OS X version 10.5 or later is needed for use of property
> Modules/objc/test/properties.m:26: warning: Mac OS X version 10.5 or later is needed for use of property
> Modules/objc/test/properties.m:27: warning: Mac OS X version 10.5 or later is needed for use of property
> Modules/objc/test/properties.m:27: warning: no 'assign', 'retain', or 'copy' attribute is specified - 'assign' is assumed
> Modules/objc/test/properties.m:27: warning: 'assign' attribute (default) not appropriate for non-gc object property 'prop4'

This is not a problem for using pyobjc, the warnings are for parts of the unittests for pyobjc-core.

> 
> 
> It is 10.5.  system_profiler says "System Version: Mac OS X 10.5.8 (9L31a) )"
> 
> And finally:
> 
> Skipping installation of build/bdist.macosx-10.4-i386/egg/PyObjCTest/__init__.py (namespace package)
> Skipping installation of build/bdist.macosx-10.4-i386/egg/PyObjCTest/arrays.so (namespace package)
> Skipping installation of build/bdist.macosx-10.4-i386/egg/PyObjCTest/block.so (namespace package)
> Skipping installation of build/bdist.macosx-10.4-i386/egg/PyObjCTest/cfsocket.so (namespace package)
> Skipping installation of build/bdist.macosx-10.4-i386/egg/PyObjCTest/clinmeth.so (namespace package)
> ... another 90-100 lines of this, some for .so and some for .py files
> Skipping installation of build/bdist.macosx-10.4-i386/egg/PyObjCTest/testclassandinst.so (namespace package)
> Skipping installation of build/bdist.macosx-10.4-i386/egg/PyObjCTest/testoutputinitializer.so (namespace package)
> Skipping installation of build/bdist.macosx-10.4-i386/egg/PyObjCTest/voidpointer.so (namespace package)
> Adding pyobjc-core 2.3 to easy-install.pth file
> 
> Installed /Users/sienkiew/py/lib/python2.7/site-packages/pyobjc_core-2.3-py2.7-macosx-10.4-i386.egg
> Processing dependencies for pyobjc-core==2.3
> Finished processing dependencies for pyobjc-core==2.3

This looks OK.

> 
> 
> The easy_install step did not produce a working pyobjc:
> 
>>>> import pyobjc
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> ImportError: No module named pyobjc

That's expected. Use 'import objc' instead.
> 
> 
> 
> At this point, I'm thinking there must be something odd about my system that two different versions do not work at all, even when installed with easy_install.  Unfortunately, I don't really know enough about easy_install to know what questions to ask next.  Do you have any suggestions?

You seem the end up with a complete installation. Does 'import Foundation' or 'import AppKit' work?

Ronald
> 
> Mark S.
>