On Dec 20, 2010, at 3:47 PM, Ryan Schmidt wrote: > Seeing the config.log might be interesting, but it will probably just confirm > that you don't seem to have an acceptable C compiler, though it seemed to > identify that you do have Xcode 3.2.5. Did you install Xcode in a nonstandard > location? If so, tell MacPorts of it by editing the developer_dir setting in > macports.conf. Or did you omit the UNIX development tools when installing > Xcode? If so, install Xcode again, including those components; they're > required for MacPorts.
Well, that was the answer. After loosing that HD the Time Machine restore evidently "lost" or "corrupted" something. A complete download and re-install f Xcode 3.2.5 fixed everything. [Default installation, re-installed everything, including Unix tools.] T.T.F.N. William H. Magill # Flat-panel iMac (2.1) [800MHz - Super Drive - 768 Meg] OS X 10.4.11 # iMac6,1 Core 2 Duo [2.16GHz - 3 GB 667] OS X 10.6.5 # MacBook Pro4.1 Core 2 Duo [2.5GHz - 4GB 667] OS X 10.6.5 # Mac mini Core Duo [1.66 Ghz - 2 GB 667]OS X 10.6.5 # PWS433a [Alpha 21164 Rev 7.2 (EV56)- 64 Meg] Tru64 5.1a # XP1000 [Alpha 21264-3 (EV6) - 256 meg] FreeBSD 5.3 # XP1000 [Alpha 21264-A (EV6-7) - 256 meg] FreeBSD 5.3 [email protected] [email protected] [email protected] _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
