id summary reporter owner description type status priority milestone component version resolution keywords cc port 12794 MacPorts should warn of old Xcode versions ryandesign macports-tickets@… "We [http://lists.macosforge.org/pipermail/macports-dev/2007-July/002265.html have the problem] that from time to time, although we say in InstallingMacPorts that people must install the latest Xcode, they don't, and they end up using an older Xcode. Then they run into weird problems that we waste time investigating. This happened recently in #12219 where someone couldn't install gcc42, and [http://lists.macosforge.org/pipermail/macports-users/2007-September/005723.html on the mailing list] someone reported being unable to install wine. Both issues were resolved by installing Xcode 2.4.1. MacPorts should catch this before it ever gets to Trac or the mailing list. It should either print a warning when the Xcode version is known to be outdated, or it should refuse to proceed altogether until it's updated. Landon [http://lists.macosforge.org/pipermail/macports-dev/2007-July/002267.html objected] to the latter saying users will be put off by such a large download, but Blair [http://lists.macosforge.org/pipermail/macports-dev/2007-July/002270.html countered] that developer time is valuable and we shouldn't waste it trying to re-solve problems that we already know are solved by upgrading Xcode. We know at this point that Xcode 1.5 and 2.4.1 are fine for Mac OS X 10.3.9 and 10.4.10, respectively, so any Xcode versions earlier than those should trigger the new behavior. Alternately, Blair says Fink contains code that identifies specific bad versions of gcc, which we could look at doing too." defect closed Normal MacPorts 1.9.0 base 1.5.2 fixed wiml@…