On May 15, 2012, at 11:26 PM, Ryan Schmidt wrote:
> On May 16, 2012, at 01:13, Adam Dershowitz wrote: > >> Thanks. Sounds simple enough, although one question. I had 2.0.?. It >> crashed before I upgraded to 2.1.0. So I assume that I should instead us an >> older installer, then once all is working do the upgrade to 2.1.0. Or will >> the 2.1.0 installer be fine now and it will upgrade fine? > > It doesn't matter what installer version you use; when it's done, you'll have > the current version, 2.1.0 (because the installer ends by running > selfupdate). It should be fine either way. > And, I have another problem, that is only partially related to macports, but figured I would ask. When I went to install macports 2.1, it complained that I didn't have xcode installed. I checked, and while my developer folder is present, and seems correct, after my restore, it seems like that command line tools are not present. At least if I do gcc, nothing happens (same with which gcc). Any idea if that is just a missing link, or something else? I started download xcode_3.2.5 again, but it is going to take a bunch of hours, so figured I would ask if anyone has an easier solution, since clearly most, if not all, of xcode is already installed. It seems that there might be an easier way, short of the full reinstall of xcode. Thanks, --Adam _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
