Excuse me, but there is something completely messed with ports. It should take the path out of xcode-select.
root:/> xcode-select -print-path /Applications/Utilities/Xcode.app/Contents/Developer root:/> xcodebuild -version Xcode 4.3.2 Build version 4E2002 root:/> echo $PATH /Applications/Utilities/Xcode.app/Contents/Developer/usr/bin/:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/sw/bin:/sw/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/X11/bin:/usr/local/bin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin root:/> port install sshfs Error: The installed version of Xcode (2.0orlower) is too old to use on the installed OS version. Version 4.1 or later is recommended on Mac OS X 10.7. Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> Am 14. April 2012 11:08 schrieb Joshua Root <[email protected]>: > On 2012-4-14 18:50 , Elmar Stellnberger wrote: >> Quite a Hazard: >> macports refuses to compile since I have installed Kenneth Reitz`s >> homebrew gcc although >> the latest console tools and Xcode are installed correctly (fink does >> quite well that way). >> >>> xcode-select -print-path >> /Applications/Utilities/Xcode.app/Contents/Developer >>> port install sshfs >> Error: The installed version of Xcode (2.0orlower) is too old to use >> on the installed OS version. Version 4.1 or later is recommended on >> Mac OS X 10.7. > > This check is based on the output of 'xcodebuild -version', and if that > doesn't produce something we can parse, there's something wrong with > your Xcode installation. > > - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
