#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 hmijail@…):
There are a number of suggestions in
http://stackoverflow.com/questions/9323738/unable-to-get-macport- functionality-after-installing-xcode-4-3
I have tried the 2 most sane-looking of them:
-- sudo /usr/bin/xcode-select -switch /Applications/Xcode.app
(interesting that after this, xcode-select -print-path shows
/Applications/Xcode.app/'''Contents/Developer''');
--and changing developer_dir in macports.conf to
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
With this, I can now install at least some ports without any warning. I
have found a problem in for example libvpx, but I am not sure if this is a
problem in the port itself.
Note, I am using ccache and parallel builds, so my environment might be
more demanding than "normal".
--
Ticket URL: <
https://trac.macports.org/ticket/33280#comment:11>
MacPorts <
http://www.macports.org/>
Ports system for Mac OS
_______________________________________________
macports-tickets mailing list
macports-tickets@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-tickets
