[MacPorts] #16511: zeroinstall-injector fails with pygtk problem

MacPorts noreply at macports.org
Thu Sep 11 06:43:08 PDT 2008


#16511: zeroinstall-injector fails with pygtk problem
-----------------------------------+----------------------------------------
  Reporter:  wsc9tt at gmail.com      |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect                |      Status:  new                                  
  Priority:  Normal                |   Milestone:  Port Bugs                            
 Component:  ports                 |     Version:  1.6.0                                
Resolution:                        |    Keywords:  pygtk                                
      Port:  zeroinstall-injector  |  
-----------------------------------+----------------------------------------

Comment(by wsc9tt at gmail.com):

 Interesting.  The first half of the problem is that zeroinstall was using
 the wrong python.

 I don't have /opt/local/bin first in my path so it appears that 0install
 was relaunching
 python without using the macports version that is depends on.  It either
 got the mac's /usr/bin/python
 or fink's /sw/bin/python2.5

 When launching with the right PATH I get something like this:

 mbp ~ $ PATH=/opt/local/bin:$PATH 0launch --gui
 The process has forked and you cannot use this CoreFoundation
 functionality safely. You MUST exec().
 Break on
 __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
 to debug.
 The process has forked and you cannot use this CoreFoundation
 functionality safely. You MUST exec().
 Break on
 __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
 to debug.
 The process has forked and you cannot use this CoreFoundation
 functionality safely. You MUST exec().
 Break on
 __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
 to debug.
 The process has forked and you cannot use this CoreFoundation
 functionality safely. You MUST exec().
 Break on
 __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
 to debug.
 The process has forked and you cannot use this CoreFoundation
 functionality safely. You MUST exec().
 Break on
 __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
 to debug.

 where it then has a fault in python.

-- 
Ticket URL: <http://trac.macports.org/ticket/16511#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list