[MacPorts] #13287: py-pyobjc fails to build on Mac OS X 10.5 Leopard

MacPorts trac at macosforge.org
Wed Nov 21 10:16:07 PST 2007


#13287: py-pyobjc fails to build on Mac OS X 10.5 Leopard
--------------------------------------+-------------------------------------
  Reporter:  nathan.stocks at gmail.com  |       Owner:  macports-dev at lists.macosforge.org
      Type:  defect                   |      Status:  new                              
  Priority:  High                     |   Milestone:  Port Bugs                        
 Component:  ports                    |     Version:  1.5.2                            
Resolution:                           |    Keywords:                                   
--------------------------------------+-------------------------------------
Comment (by nathan.stocks at gmail.com):

 Yes, absolutely, I would love for you to help out in any way.  I have no
 idea how to get this working.  I just want to use py-game, which depends
 on pyobjc.

 FYI, here's some things that people have told me on the mailing lists:

 Ben Artin to me, pyobjc-dev
 > What's the status of Leopard support for pyobjc?

 It's included with the OS, as is Python 2.5.1.

 ------------

 Ben Artin to me, pyobjc-dev


 > Hmmm, so...then I suppose the bug with Macports is that it's trying to
 > build it as a dependency of py-game at all?

 It depends on what the MacPorts policy on such things is; I believe in
 the past they've always relied on their own build of Python and
 associated libraries. They may continue doing so on Leopard.

 The problem that you will run into is that the pyobjc package in
 MacPorts currently has no maintainer, so if you want to get it changed
 (for example, by updating it to pyobjc2), you'll probably have to do
 the work yourself or wait for someone in a similar predicament to do
 it for you.

 > Maybe I can modify the py-game portfile myself and remove the pyobjc
 > 1.4 dependency.

 That will give you a pygame in MacPorts' package folder rather than
 the system package folder; this is not the right thing, but it may get
 you closer to being able to ignore the problem -- or it may not work
 at all. Depends on how complex pygame is.

 ------------

 Ronald Oussoren to me, Ben, pyobjc-dev

 PyObjC 1.4 does not support Leopard and never will.  I have no idea if
 pygame works with PyObjC 2.0.

 BTW. AFAIK there is no macports portfile for PyObjC 2.0, and that wouldn't
 make much sense until PyObjC 2.0 supports Tiger as well.

 ------------

 Ronald Oussoren to James, pyobjc-dev

 On Wednesday, November 21, 2007, at 04:40PM, "James R Eagan"
 <eaganj at bazza.com> wrote:
 >On Nov 21, 2007, at 01:46 , Ronald Oussoren wrote:
 >
 >> PyObjC 1.4 does not support Leopard and never will.
 >
 >Are you saying that (1) PyObjC 1.4 will never be installable and
 >usable for developing applications on Leopard, (2) that applications
 >built using PyObjC 1.4 [on Tiger] will not run properly on Leopard, or
 >(3) both?

 I meant (1), if you build PyObjC on Tiger it should work on Leopard.

-- 
Ticket URL: <http://trac.macports.org/projects/macports/ticket/13287#comment:3>
MacPorts </projects/macports>
Ports system for Mac OS


More information about the macports-tickets mailing list