Clearing up the confusion: This person is referring to the Homebrew package manager.
He mistakenly thinks that because Homebrew works with only the commandline tools installed, that MacPorts should as well. As you stated, a full Xcode install is necessary. Each package manager on OS X (MacPorts, Fink, Pkgsrc, Homebrew, Prefix, Rubygems) has a different set of rules and requirements. You must pay attention to the details for each. Art > On 04/12/2012 03:57 PM, Elmar Stellnberger wrote: >> Unfortunately now the build error has changed: >>> port install macfuse >> 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> > > This means you do not have any xcodebuild binary and thus, this is not > considered a complete Xcode installation. > >> That is I have installed both: Homebrew and Apple`s Xcode, but >> xcode-select -switch /Applications/Utilities/Xcode.app/Contents/Developer/ >> does not have any effect on ports. > > What is "Homebrew's Xcode"? > >> At least it should be possible to select the required compiler. >> I wonder why building gcc47 has worked before without this error. >> As said before I would appreciate a set of base packages like building gcc47 >> would be supported without having to run utils like xcode-build. >> gcc47 does compile with this compiler release and it should be possible to >> skip this error message!! > > In its current implementation, MacPorts expects a full Xcode installation. > > Rainer _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev