Thread: [Pyobjc-dev] New beta release for pyobjc: 2.2b2
Brought to you by:
ronaldoussoren
Menu
▾
▴
pyobjc-dev
|
From: Ronald O. <ron...@ma...> - 2009-05-26 10:00:49
Attachments:
smime.p7s
|
Hi, I've just pushed out a new beta release for PyObjC 2.2. This version should install without problems using "easy_install pyobjc==2.2b2", and fixes some other smallish issues as well. Support for OSX 10.4 is still fairly minimal: pyobjc-core and a number of framework wrappers do build on Tiger, but there are a lot of test failures (although a large subset of those are caused by issues in the test framework). Support for OSX 10.6 is non-existant for now due to the obvious reason ;-) Ronald |
|
From: Ron G. <ro...@fl...> - 2009-05-26 17:29:40
|
On May 26, 2009, at 2:59 AM, Ronald Oussoren wrote: > Hi, > > I've just pushed out a new beta release for PyObjC 2.2. This version > should install without problems using "easy_install pyobjc==2.2b2", > and fixes some other smallish issues as well. > > Support for OSX 10.4 is still fairly minimal: pyobjc-core and a > number of framework wrappers do build on Tiger, but there are a lot > of test failures (although a large subset of those are caused by > issues in the test framework). > > Support for OSX 10.6 is non-existant for now due to the obvious > reason ;-) It still doesn't work for me (on an Macbook Pro (Intel) running 10.5.7): [ron@mickey:~]$ sudo easy_install pyobjc==2.2b2 Searching for pyobjc==2.2b2 Best match: pyobjc 2.2b2 Processing pyobjc-2.2b2-py2.6.egg pyobjc 2.2b2 is already the active version in easy-install.pth Using /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ site-packages/pyobjc-2.2b2-py2.6.egg Processing dependencies for pyobjc==2.2b2 Searching for pyobjc-framework-ScreenSaver==2.2b2 Reading http://pypi.python.org/simple/pyobjc-framework-ScreenSaver/ Reading http://pyobjc.sourceforge.net Best match: pyobjc-framework-ScreenSaver 2.2b2 Downloading http://pypi.python.org/packages/source/p/pyobjc-framework-ScreenSaver/pyobjc-framework-ScreenSaver-2.2b2.tar.gz#md5 =bff19c85e265409701c684f463e16c78 Processing pyobjc-framework-ScreenSaver-2.2b2.tar.gz Running pyobjc-framework-ScreenSaver-2.2b2/setup.py -q bdist_egg -- dist-dir /var/folders/nT/nTiypn-v2RatkU+BYncrKU+++TI/-Tmp-/ easy_install-1khDIF/pyobjc-framework-ScreenSaver-2.2b2/egg-dist-tmp- Sy04w1 /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ distutils/dist.py:266: UserWarning: Unknown distribution option: 'options' warnings.warn(msg) ld: in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/libTIFF.dylib, file is not of required architecture for architecture ppc collect2: ld returned 1 exit status lipo: can't open input file: /var/folders/nT/nTiypn-v2RatkU+BYncrKU++ +TI/-Tmp-//ccNC2XJP.out (No such file or directory) error: Setup script exited with error: command 'gcc' failed with exit status 1 rg |
|
From: Ronald O. <ron...@ma...> - 2009-05-26 17:35:05
Attachments:
smime.p7s
|
On 26 May, 2009, at 19:29, Ron Garret wrote: > > On May 26, 2009, at 2:59 AM, Ronald Oussoren wrote: > >> Hi, >> >> I've just pushed out a new beta release for PyObjC 2.2. This >> version should install without problems using "easy_install >> pyobjc==2.2b2", and fixes some other smallish issues as well. >> >> Support for OSX 10.4 is still fairly minimal: pyobjc-core and a >> number of framework wrappers do build on Tiger, but there are a lot >> of test failures (although a large subset of those are caused by >> issues in the test framework). >> >> Support for OSX 10.6 is non-existant for now due to the obvious >> reason ;-) > > It still doesn't work for me (on an Macbook Pro (Intel) running > 10.5.7): > > [ron@mickey:~]$ sudo easy_install pyobjc==2.2b2 > Searching for pyobjc==2.2b2 > Best match: pyobjc 2.2b2 > Processing pyobjc-2.2b2-py2.6.egg > pyobjc 2.2b2 is already the active version in easy-install.pth > > Using /Library/Frameworks/Python.framework/Versions/2.6/lib/ > python2.6/site-packages/pyobjc-2.2b2-py2.6.egg > Processing dependencies for pyobjc==2.2b2 > Searching for pyobjc-framework-ScreenSaver==2.2b2 > Reading http://pypi.python.org/simple/pyobjc-framework-ScreenSaver/ > Reading http://pyobjc.sourceforge.net > Best match: pyobjc-framework-ScreenSaver 2.2b2 > Downloading http://pypi.python.org/packages/source/p/pyobjc-framework-ScreenSaver/pyobjc-framework-ScreenSaver-2.2b2.tar.gz#md5 > =bff19c85e265409701c684f463e16c78 > Processing pyobjc-framework-ScreenSaver-2.2b2.tar.gz > Running pyobjc-framework-ScreenSaver-2.2b2/setup.py -q bdist_egg -- > dist-dir /var/folders/nT/nTiypn-v2RatkU+BYncrKU+++TI/-Tmp-/ > easy_install-1khDIF/pyobjc-framework-ScreenSaver-2.2b2/egg-dist-tmp- > Sy04w1 > /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ > distutils/dist.py:266: UserWarning: Unknown distribution option: > 'options' > warnings.warn(msg) > ld: in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/libTIFF.dylib, > file is not of required architecture for architecture ppc > collect2: ld returned 1 exit status > lipo: can't open input file: /var/folders/nT/nTiypn-v2RatkU+BYncrKU++ > +TI/-Tmp-//ccNC2XJP.out (No such file or directory) > error: Setup script exited with error: command 'gcc' failed with > exit status 1 You have non-universal libraries in /usr/local, but I don't understand why this is a problem because that library shouldn't be used at all. What's even more odd is that python tries to compile at all, there are binary eggs available for python2.6. Ronald > > rg > |
|
From: Ron G. <ro...@fl...> - 2009-05-26 18:26:14
|
On May 26, 2009, at 10:34 AM, Ronald Oussoren wrote: > > On 26 May, 2009, at 19:29, Ron Garret wrote: > >> >> On May 26, 2009, at 2:59 AM, Ronald Oussoren wrote: >> >>> Hi, >>> >>> I've just pushed out a new beta release for PyObjC 2.2. This >>> version should install without problems using "easy_install >>> pyobjc==2.2b2", and fixes some other smallish issues as well. >>> >>> Support for OSX 10.4 is still fairly minimal: pyobjc-core and a >>> number of framework wrappers do build on Tiger, but there are a >>> lot of test failures (although a large subset of those are caused >>> by issues in the test framework). >>> >>> Support for OSX 10.6 is non-existant for now due to the obvious >>> reason ;-) >> >> It still doesn't work for me (on an Macbook Pro (Intel) running >> 10.5.7): >> >> [ron@mickey:~]$ sudo easy_install pyobjc==2.2b2 >> Searching for pyobjc==2.2b2 >> Best match: pyobjc 2.2b2 >> Processing pyobjc-2.2b2-py2.6.egg >> pyobjc 2.2b2 is already the active version in easy-install.pth >> >> Using /Library/Frameworks/Python.framework/Versions/2.6/lib/ >> python2.6/site-packages/pyobjc-2.2b2-py2.6.egg >> Processing dependencies for pyobjc==2.2b2 >> Searching for pyobjc-framework-ScreenSaver==2.2b2 >> Reading http://pypi.python.org/simple/pyobjc-framework-ScreenSaver/ >> Reading http://pyobjc.sourceforge.net >> Best match: pyobjc-framework-ScreenSaver 2.2b2 >> Downloading http://pypi.python.org/packages/source/p/pyobjc-framework-ScreenSaver/pyobjc-framework-ScreenSaver-2.2b2.tar.gz#md5 >> =bff19c85e265409701c684f463e16c78 >> Processing pyobjc-framework-ScreenSaver-2.2b2.tar.gz >> Running pyobjc-framework-ScreenSaver-2.2b2/setup.py -q bdist_egg -- >> dist-dir /var/folders/nT/nTiypn-v2RatkU+BYncrKU+++TI/-Tmp-/ >> easy_install-1khDIF/pyobjc-framework-ScreenSaver-2.2b2/egg-dist-tmp- >> Sy04w1 >> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ >> distutils/dist.py:266: UserWarning: Unknown distribution option: >> 'options' >> warnings.warn(msg) >> ld: in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/libTIFF.dylib, >> file is not of required architecture for architecture ppc >> collect2: ld returned 1 exit status >> lipo: can't open input file: /var/folders/nT/nTiypn-v2RatkU+BYncrKU+ >> ++TI/-Tmp-//ccNC2XJP.out (No such file or directory) >> error: Setup script exited with error: command 'gcc' failed with >> exit status 1 > > > You have non-universal libraries in /usr/local, but I don't > understand why this is a problem because that library shouldn't be > used at all. > > What's even more odd is that python tries to compile at all, there > are binary eggs available for python2.6. > > Ronald I'm not quite sure what to make of this response. It seems to me that if a Python library is trying to find a PPC binary on an Intel machine that's a bug in the Python library. Also it's looking in the MacOSX10.4u.sdk directory, but this machine is running 10.5 (.7), which seems like another bug. So... is this a bug, or am I doing something stupid? If it's a bug, am I the only person encountering it? Can I do anything to help fix it? rg |
|
From: Ronald O. <ron...@ma...> - 2009-05-26 18:35:19
Attachments:
smime.p7s
|
On 26 May, 2009, at 20:25, Ron Garret wrote: > > On May 26, 2009, at 10:34 AM, Ronald Oussoren wrote: > >> >> On 26 May, 2009, at 19:29, Ron Garret wrote: >> >>> >>> On May 26, 2009, at 2:59 AM, Ronald Oussoren wrote: >>> >>>> Hi, >>>> >>>> I've just pushed out a new beta release for PyObjC 2.2. This >>>> version should install without problems using "easy_install >>>> pyobjc==2.2b2", and fixes some other smallish issues as well. >>>> >>>> Support for OSX 10.4 is still fairly minimal: pyobjc-core and a >>>> number of framework wrappers do build on Tiger, but there are a >>>> lot of test failures (although a large subset of those are caused >>>> by issues in the test framework). >>>> >>>> Support for OSX 10.6 is non-existant for now due to the obvious >>>> reason ;-) >>> >>> It still doesn't work for me (on an Macbook Pro (Intel) running >>> 10.5.7): >>> >>> [ron@mickey:~]$ sudo easy_install pyobjc==2.2b2 >>> Searching for pyobjc==2.2b2 >>> Best match: pyobjc 2.2b2 >>> Processing pyobjc-2.2b2-py2.6.egg >>> pyobjc 2.2b2 is already the active version in easy-install.pth >>> >>> Using /Library/Frameworks/Python.framework/Versions/2.6/lib/ >>> python2.6/site-packages/pyobjc-2.2b2-py2.6.egg >>> Processing dependencies for pyobjc==2.2b2 >>> Searching for pyobjc-framework-ScreenSaver==2.2b2 >>> Reading http://pypi.python.org/simple/pyobjc-framework-ScreenSaver/ >>> Reading http://pyobjc.sourceforge.net >>> Best match: pyobjc-framework-ScreenSaver 2.2b2 >>> Downloading http://pypi.python.org/packages/source/p/pyobjc-framework-ScreenSaver/pyobjc-framework-ScreenSaver-2.2b2.tar.gz#md5 >>> =bff19c85e265409701c684f463e16c78 >>> Processing pyobjc-framework-ScreenSaver-2.2b2.tar.gz >>> Running pyobjc-framework-ScreenSaver-2.2b2/setup.py -q bdist_egg -- >>> dist-dir /var/folders/nT/nTiypn-v2RatkU+BYncrKU+++TI/-Tmp-/ >>> easy_install-1khDIF/pyobjc-framework-ScreenSaver-2.2b2/egg-dist- >>> tmp-Sy04w1 >>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ >>> distutils/dist.py:266: UserWarning: Unknown distribution option: >>> 'options' >>> warnings.warn(msg) >>> ld: in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/ >>> libTIFF.dylib, file is not of required architecture for >>> architecture ppc >>> collect2: ld returned 1 exit status >>> lipo: can't open input file: /var/folders/nT/nTiypn-v2RatkU+BYncrKU >>> +++TI/-Tmp-//ccNC2XJP.out (No such file or directory) >>> error: Setup script exited with error: command 'gcc' failed with >>> exit status 1 >> >> >> You have non-universal libraries in /usr/local, but I don't >> understand why this is a problem because that library shouldn't be >> used at all. >> >> What's even more odd is that python tries to compile at all, there >> are binary eggs available for python2.6. >> >> Ronald > > I'm not quite sure what to make of this response. It seems to me > that if a Python library is trying to find a PPC binary on an Intel > machine that's a bug in the Python library. Also it's looking in > the MacOSX10.4u.sdk directory, but this machine is running 10.5 (. > 7), which seems like another bug. The compiler isn't that smart. If the linker looks for a library and stops at the first filename that matches without looking if it is for the right architecture. That means that if you happen to have a PPC library in /usr/local/lib and the compiler was actually looking for an intel one the search stops at the PPC library and you get a link error. If you have installed Python using the installer from the python.org site the situation is slightly more complicated: that installs a universal binary, which is a fat binary that contains both intel and ppc versions of the code. This means that all libraries that get linked into extensions must also be universal binaries and if they aren't you'll get link errors. > > So... is this a bug, or am I doing something stupid? If it's a bug, > am I the only person encountering it? Can I do anything to help fix > it? Can you manually download the source archive of pyobjc-framework- ScreenSaver from pypi.python.org and sent me the result of "python2.6 setup.py install. I'd also like to see the output of "file /usr/local/ lib/libTIFF.dylib", "python2.6 -c 'import distutils.util; print distutils.util.get_platform()' and 'python2.6 -V'. And finally: how did you install python, from source or using a binary installer? Please sent this information off-list because it isn't relevant for most readers. Ronald > > rg > |
|
From: friendship7 <fri...@gm...> - 2009-05-27 06:25:38
|
2009/5/26 Ronald Oussoren <ron...@ma...>: > > The compiler isn't that smart. If the linker looks for a library and stops > at the first filename that matches without looking if it is for the right > architecture. That means that if you happen to have a PPC library in > /usr/local/lib and the compiler was actually looking for an intel one the > search stops at the PPC library and you get a link error. > > If you have installed Python using the installer from the python.org site > the situation is slightly more complicated: that installs a universal > binary, which is a fat binary that contains both intel and ppc versions of > the code. This means that all libraries that get linked into extensions must > also be universal binaries and if they aren't you'll get link errors. Oh, please, I'm in this situation: python 2.6 from python.org, OSX 10.5. Two things: setuptools (if I'm right) build C extensions against the 10.4u SDK and not 10.5, and chokes on intel only libraries that it needs to link the stub against. Where, in python, setuptools I think, can I tweak those compiler defaults: -isysroot /Developper/.../10.4u -arch i386 -arch ppc to: -isysroot /Developper/.../10.5 -arch i386 I know pyobjc will fail compiling if I can't change it. Regards. |
|
From: Leonardo S. <san...@gm...> - 2009-05-27 03:16:33
|
On May 26, 2009, at 6:59 AM, Ronald Oussoren wrote: > Hi, > > I've just pushed out a new beta release for PyObjC 2.2. This version > should install without problems using "easy_install pyobjc==2.2b2", > and fixes some other smallish issues as well. > > Support for OSX 10.4 is still fairly minimal: pyobjc-core and a > number of framework wrappers do build on Tiger, but there are a lot > of test failures (although a large subset of those are caused by > issues in the test framework). > > Support for OSX 10.6 is non-existant for now due to the obvious > reason ;-) > > Ronald It would be nice if the packager of pyobjc for macports posts here when the portfile is released so we (macports users) can know when this is avaliable to us. -- Leonardo Santagada santagada at gmail.com |
|
From: Ronald O. <ron...@ma...> - 2009-05-27 21:10:05
Attachments:
smime.p7s
|
On 27 May, 2009, at 8:25, friendship7 wrote: > 2009/5/26 Ronald Oussoren <ron...@ma...>: >> >> The compiler isn't that smart. If the linker looks for a library >> and stops >> at the first filename that matches without looking if it is for the >> right >> architecture. That means that if you happen to have a PPC library in >> /usr/local/lib and the compiler was actually looking for an intel >> one the >> search stops at the PPC library and you get a link error. >> >> If you have installed Python using the installer from the >> python.org site >> the situation is slightly more complicated: that installs a universal >> binary, which is a fat binary that contains both intel and ppc >> versions of >> the code. This means that all libraries that get linked into >> extensions must >> also be universal binaries and if they aren't you'll get link errors. > > Oh, please, I'm in this situation: python 2.6 from python.org, OSX > 10.5. > Two things: setuptools (if I'm right) build C extensions against the > 10.4u SDK and > not 10.5, and chokes on intel only libraries that it needs to link the > stub against. > > Where, in python, setuptools I think, can I tweak those compiler > defaults: > > -isysroot /Developper/.../10.4u > -arch i386 -arch ppc > > to: > > -isysroot /Developper/.../10.5 > -arch i386 > > I know pyobjc will fail compiling if I can't change it. I provide precompiled binaries that will be used if you have Python 2.6.2 from the python.org site (that's what I used to build those eggs). It seems that 2.6.1 still contains a bug that makes it use the wrong platform string in distutils, which might explain your problem. I'm also looking in a way to make the build machinary not look into / usr/local for dependencies, but that's harder than I'd like. Ronald |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X