Thread: [Pyobjc-dev] Got a problem to install PyObjC2.0
Brought to you by:
ronaldoussoren
Menu
▾
▴
pyobjc-dev
|
From: Seungchan O. <seu...@gm...> - 2007-11-08 06:14:13
|
Hello, I'm having a difficulty to install PyObjC2.0 at Leopard with MacBook Pro. I downloaded the source files from http://svn.red-bean.com/pyobjc/tags/r200-leopard And the command is python setup.py bdist_mpkg --open The part of message is ====================================================== gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c libffi-src/powerpc/ppc-ffi_darwin.c -o build/temp.macosx- 10.3-fat-2.5/libffi-src/powerpc/ppc-ffi_darwin.o -DPyObjC_STRICT_DEBUGGING -DMACOSX -no-cpp-precomp -Wno-long-double -g -O1 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wformat=2 -W -Wshadow -Wpointer-arith -Wmissing-declarations -Wnested-externs -Wno-long-long -Wno-import -I/usr/include/libxml2 -Ibuild/codegen/ -Ilibffi-src/include -Ilibffi-src/powerpc libffi-src/powerpc/ppc-ffi_darwin.c:41:67: error: libkern/OSCacheControl.h: No such file or directory libffi-src/powerpc/ppc-ffi_darwin.c:86: warning: no previous prototype for 'ffi_prep_args' libffi-src/powerpc/ppc-ffi_darwin.c: In function 'ffi_prep_closure': libffi-src/powerpc/ppc-ffi_darwin.c:751: warning: implicit declaration of function 'sys_icache_invalidate' libffi-src/powerpc/ppc-ffi_darwin.c:751: warning: nested extern declaration of 'sys_icache_invalidate' libffi-src/powerpc/ppc-ffi_darwin.c: At top level: libffi-src/powerpc/ppc-ffi_darwin.c:810: warning: no previous prototype for 'ffi_closure_helper_DARWIN' libffi-src/powerpc/ppc-ffi_darwin.c: In function 'ffi_closure_helper_DARWIN': libffi-src/powerpc/ppc-ffi_darwin.c:845: warning: comparison between signed and unsigned libffi-src/powerpc/ppc-ffi_darwin.c:901: warning: pointer of type 'void *' used in arithmetic libffi-src/powerpc/ppc-ffi_darwin.c:901: warning: pointer of type 'void *' used in arithmetic lipo: can't figure out the architecture type of: /var/folders/+w/+wei-YpVFdGoV29uK3G3x++++TI/-Tmp-//ccUuWnhU.out error: command 'gcc' failed with exit status 1 ====================================================== I'm new to the PyObjC. Any comments will help me a lot. Thanks in advance, SC |
|
From: Seungchan O. <seu...@gm...> - 2007-11-08 01:01:20
|
Hello, I'm having a difficulty to install PyObjC2.0 at Leopard with MacBook Pro. I downloaded the source files from http://svn.red-bean.com/pyobjc/tags/r200-leopard And the command is python setup.py bdist_mpkg --open The part of message is ====================================================== gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c libffi-src/powerpc/ppc-ffi_darwin.c -o build/temp.macosx-10.3-fat-2.5/libffi-src/powerpc/ppc-ffi_darwin.o -DPyObjC_STRICT_DEBUGGING -DMACOSX -no-cpp-precomp -Wno-long-double -g -O1 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wformat=2 -W -Wshadow -Wpointer-arith -Wmissing-declarations -Wnested-externs -Wno-long-long -Wno-import -I/usr/include/libxml2 -Ibuild/codegen/ -Ilibffi-src/include -Ilibffi-src/powerpc libffi-src/powerpc/ppc-ffi_darwin.c:41:67: error: libkern/OSCacheControl.h: No such file or directory libffi-src/powerpc/ppc-ffi_darwin.c:86: warning: no previous prototype for 'ffi_prep_args' libffi-src/powerpc/ppc-ffi_darwin.c: In function 'ffi_prep_closure': libffi-src/powerpc/ppc-ffi_darwin.c:751: warning: implicit declaration of function 'sys_icache_invalidate' libffi-src/powerpc/ppc-ffi_darwin.c:751: warning: nested extern declaration of 'sys_icache_invalidate' libffi-src/powerpc/ppc-ffi_darwin.c: At top level: libffi-src/powerpc/ppc-ffi_darwin.c:810: warning: no previous prototype for 'ffi_closure_helper_DARWIN' libffi-src/powerpc/ppc-ffi_darwin.c: In function 'ffi_closure_helper_DARWIN': libffi-src/powerpc/ppc-ffi_darwin.c:845: warning: comparison between signed and unsigned libffi-src/powerpc/ppc-ffi_darwin.c:901: warning: pointer of type 'void *' used in arithmetic libffi-src/powerpc/ppc-ffi_darwin.c:901: warning: pointer of type 'void *' used in arithmetic lipo: can't figure out the architecture type of: /var/folders/+w/+wei-YpVFdGoV29uK3G3x++++TI/-Tmp-//ccUuWnhU.out error: command 'gcc' failed with exit status 1 ====================================================== I'm new to the PyObjC. Any comments will help me a lot. Thanks in advance, SC |
|
From: Ronald O. <ron...@ma...> - 2007-11-08 07:19:43
Attachments:
smime.p7s
|
On 8 Nov, 2007, at 7:14, Seungchan Oh wrote: > Hello, > > I'm having a difficulty to install PyObjC2.0 at Leopard with MacBook > Pro. I haven't tried building on 10.4 for a while (which is what you're basicly trying to do because you're using the 10.4 SDK). Appearently there are some issues there. Note that PyObjC 2.0 definitely requires some work to be useful on Tiger systems because Tiger doesn't ship with bridgesupport files and PyObjC 2 requires those files to provide full bindings. Generating bridgesupport files is easy enough, but not a priority for me right now because building them takes a lot of time (for the computer, the task barely requires interaction with a human) and I'm currently thinking about some changes that would require rebuilding the bridgesupport files anyway. BTW. You do know that Leopard ships with a perfectly fine copy of Python 2.5 and PyObjC 2.0? At this point in time it would be easier to use that instead of trying to rebuild PyObjC from scratch. Ronald |
|
From: Luc H. <lu...@ho...> - 2007-11-08 08:05:05
|
On 8 nov. 07, at 08:19, Ronald Oussoren wrote: > BTW. You do know that Leopard ships with a perfectly fine copy of > Python 2.5 and PyObjC 2.0? At this point in time it would be easier > to use that instead of trying to rebuild PyObjC from scratch. Unless your PyObjC application needs to run on 10.5 AND 10.4, right ? I haven't tried it yet, but I wouldn't expect a PyObjC2/py2app application built on Leopard to run on Tiger as-is. -- Luc Heinrich |
|
From: Ronald O. <ron...@ma...> - 2007-11-08 08:20:14
Attachments:
smime.p7s
|
On 8 Nov, 2007, at 9:04, Luc Heinrich wrote: > On 8 nov. 07, at 08:19, Ronald Oussoren wrote: > >> BTW. You do know that Leopard ships with a perfectly fine copy of >> Python 2.5 and PyObjC 2.0? At this point in time it would be easier >> to use that instead of trying to rebuild PyObjC from scratch. > > Unless your PyObjC application needs to run on 10.5 AND 10.4, right ? > I haven't tried it yet, but I wouldn't expect a PyObjC2/py2app > application built on Leopard to run on Tiger as-is. Go read the rest of my message. PyObjC2 requires some additional work to be useful on Tiger. BTW. The only truly save way to build a Python app bundle that works on Tiger at the moment is by building all extensions (PyObjC, wxPython, numpy, ...) on Tiger. Building the actual app bundle can safely be done on Leopard, but you must extensions (anything that requires a C compiler) on Tiger. In theory it should be possible to build extensions on Leopard as well, but AFAIK nobody has fully tested that and you might therefore run into problems when you do that. That said, Python itself is build on a Tiger systems and runs on Panther as well, including all extensions. Ronald |
|
From: Ben A. <be...@ar...> - 2007-11-08 15:50:49
|
On Nov 8, 2007, at 3:20 AM, Ronald Oussoren wrote: > BTW. The only truly save way to build a Python app bundle that works > on Tiger at the moment is by building all extensions (PyObjC, > wxPython, numpy, ...) on Tiger. Building the actual app bundle can > safely be done on Leopard, but you must extensions (anything that > requires a C compiler) on Tiger. Actually, that's not entirely true; it's only safe to build the app bundle on Leopard if you are building a standalone app. If you build a semi-standalone app, your .py files will be compiled with the Python 2.5 in /System, which the Python 2.3 in Tiger can't run. -- <http://artins.org/ben> "Computers! All they ever think of is hex!" |
|
From: Barry W. <bar...@gm...> - 2007-11-09 00:10:48
Attachments:
out.txt
|
Given recent traffic on the pythonmac-sig, it sounds like the system python on Leopard goes out of its way to put the site-packages directory in /Library last on the sys.path. So, if we want to write python apps that use newer versions of, e.g., numpy than those that shipped with Leopard, we're SOL unless we want to go through some PYTHONPATH contortions. The easy solution is to install MacPython into /Library/Frameworks. Then the system python and the user-updated python can be easily separated. I've so far been unable to install pyobjc2 on Leopard using MacPython 2.5.1. It sounds like I'm having similar problems to the OP (output of ./02-develop-all.sh is included; is 02-develop-all.sh the correct way to build/install the entire package?). As Ronald mentioned, it looks like this is because the 10.4u SDK is being used. Is there a way to specify building using the 10.5 SDK and will this build work with the MacPython 2.5.1 (dowloaded as a DMG from python.org) which is presumably built with the 10.4u SDK? thanks, Barry On Nov 7, 2007 11:19 PM, Ronald Oussoren <ron...@ma...> wrote: > > On 8 Nov, 2007, at 7:14, Seungchan Oh wrote: > > > Hello, > > > > I'm having a difficulty to install PyObjC2.0 at Leopard with MacBook > > Pro. > > I haven't tried building on 10.4 for a while (which is what you're > basicly trying to do because you're using the 10.4 SDK). Appearently > there are some issues there. > > Note that PyObjC 2.0 definitely requires some work to be useful on > Tiger systems because Tiger doesn't ship with bridgesupport files and > PyObjC 2 requires those files to provide full bindings. Generating > bridgesupport files is easy enough, but not a priority for me right > now because building them takes a lot of time (for the computer, the > task barely requires interaction with a human) and I'm currently > thinking about some changes that would require rebuilding the > bridgesupport files anyway. > > BTW. You do know that Leopard ships with a perfectly fine copy of > Python 2.5 and PyObjC 2.0? At this point in time it would be easier to > use that instead of trying to rebuild PyObjC from scratch. > > Ronald > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Pyobjc-dev mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyobjc-dev > > |
|
From: Barry W. <bar...@gm...> - 2007-11-19 02:25:30
|
Just a follow up to this post with a possible solution... It looks like the problem building pyobjc2 with the Framework python build from python.org was using the 10.4u SDK rather than the 10.5 SDK. Removing the "-isysroot /Developer/SKDs/MacOSX10.4u.sdk" from /Library/Python/.../lib/config/Makefile (generated by python's configure script) seems to allow pyobjc to build, and pass all unit tests using the python.org Framework build (installed in /Library/Frameworks). I'm not sure what the concequences of removing the isysroot flag from Python's Makefile are. At least for a temporary fix, it's easier than compiling a new Framework build from source. Just FYI, Barry On Nov 8, 2007 4:10 PM, Barry Wark <bar...@gm...> wrote: > Given recent traffic on the pythonmac-sig, it sounds like the system > python on Leopard goes out of its way to put the site-packages > directory in /Library last on the sys.path. So, if we want to write > python apps that use newer versions of, e.g., numpy than those that > shipped with Leopard, we're SOL unless we want to go through some > PYTHONPATH contortions. The easy solution is to install MacPython into > /Library/Frameworks. Then the system python and the user-updated > python can be easily separated. > > I've so far been unable to install pyobjc2 on Leopard using MacPython > 2.5.1. It sounds like I'm having similar problems to the OP (output > of ./02-develop-all.sh is included; is 02-develop-all.sh the correct > way to build/install the entire package?). As Ronald mentioned, it > looks like this is because the 10.4u SDK is being used. Is there a way > to specify building using the 10.5 SDK and will this build work with > the MacPython 2.5.1 (dowloaded as a DMG from python.org) which is > presumably built with the 10.4u SDK? > > thanks, > Barry > > > On Nov 7, 2007 11:19 PM, Ronald Oussoren <ron...@ma...> wrote: > > > > On 8 Nov, 2007, at 7:14, Seungchan Oh wrote: > > > > > Hello, > > > > > > I'm having a difficulty to install PyObjC2.0 at Leopard with MacBook > > > Pro. > > > > I haven't tried building on 10.4 for a while (which is what you're > > basicly trying to do because you're using the 10.4 SDK). Appearently > > there are some issues there. > > > > Note that PyObjC 2.0 definitely requires some work to be useful on > > Tiger systems because Tiger doesn't ship with bridgesupport files and > > PyObjC 2 requires those files to provide full bindings. Generating > > bridgesupport files is easy enough, but not a priority for me right > > now because building them takes a lot of time (for the computer, the > > task barely requires interaction with a human) and I'm currently > > thinking about some changes that would require rebuilding the > > bridgesupport files anyway. > > > > BTW. You do know that Leopard ships with a perfectly fine copy of > > Python 2.5 and PyObjC 2.0? At this point in time it would be easier to > > use that instead of trying to rebuild PyObjC from scratch. > > > > Ronald > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Pyobjc-dev mailing list > > Pyo...@li... > > https://lists.sourceforge.net/lists/listinfo/pyobjc-dev > > > > > |
Thanks for helping keep SourceForge clean.
X