On Apr 3, 2013, at 01:17, Lawrence Velázquez wrote: > On Apr 2, 2013, at 10:04 PM, Ryan Schmidt 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.
Oh! It hadn't occurred to me that that might happen at times other than when installing the port. I suppose that means glib2 will do this on Tiger now (#38619). > Looks like webkit-gtk fits the bill (r104778). That's the one I was thinking of. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
