On May 22, 2012, at 1:56 PM, Ryan Schmidt wrote: > > On May 21, 2012, at 22:49, LuKreme wrote: > >> On May 15, 2012, at 3:41, Harry van der Wolf <[email protected]> wrote: >>> Are these command line tools not enough for MacPorts? >> >> Nope, don't seem to be. You need Xcode and you need to do some work to >> convince macports Xcode is really installed. I decided to just roll back to >> 4.2 for now until this is all straightened out a little more. > > I think things are as straightened out now as they're going to get. To use > Xcode 4.3, you have to agree to its license agreement, and install its > command line tools afterward. I believe this is all documented in our > documentation. > >
Everything I needed to know I found at https://trac.macports.org/wiki/ProblemHotlist Just upgraded to Xcode 4.3 this morning and didn't have any problems…thanks to the hard work of so many others. That's not to say that I didn't encounter some problems, but they were all related to the fact that I'm running older versions of some ports for compatibility with a production server, but that had nothing to do with Xcode 4.3 and the documentation. Thanks to all who make MacPorts work! Phillip _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
