On Apr 2, 2013, at 10:04 PM, Ryan Schmidt <[email protected]> wrote:
> Only ports can blacklist compilers; MacPorts base itself doesn't. So you > should not have received this message when running "sudo port selfupdate", > but rather when running "sudo port upgrade". Not quite. It's possible that a port which evaluates configure.compiler at its top level has been recently updated to blacklist all Xcode 3.2.x / 4.0.x compilers. The warning would then show up when the sync portion of selfupdate evaluates that particular portfile. Looks like webkit-gtk fits the bill (r104778). vq _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
