[MacPorts] #33280: xcodebuild exists but failed to execute

MacPorts noreply at macports.org
Mon Feb 27 05:18:41 PST 2012


#33280: xcodebuild exists but failed to execute
--------------------------------------+-------------------------------------
 Reporter:  yusuf_ahmad_ali@…         |       Owner:  macports-tickets@…                   
     Type:  defect                    |      Status:  new                                  
 Priority:  Normal                    |   Milestone:                                       
Component:  base                      |     Version:  2.0.3                                
 Keywords:                            |        Port:                                       
--------------------------------------+-------------------------------------

Comment(by cal@…):

 Please revert the change to developer_dir and wait for MacPorts 2.0.4,
 fixing these things the proper way. Having developer_dir set to this path
 will make some builds fail in the release of MacPorts 2.0.4. Same thing
 goes for symlinking clang.

 The original reporter's problem is probably not having command line tools
 installed from the downloads tab in Xcode settings.

 The problem in libvpx has already been fixed (see #33283), but it might
 still not work with Xcode 4.3 and MacPorts 2.0.3.

 There is no correct way to setup MacPorts 2.0.3 in order to get it working
 fine with Xcode 4.3. Please downgrade to Xcode 4.2.1, upgrade to MacPorts
 2.0.4 as soon as it is released or run MacPorts trunk.

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


More information about the macports-tickets mailing list