On Sat, May 29, 2010 at 17:13, Joshua Root <[email protected]> wrote:
Josh > Very odd indeed. I can't replicate this with test ports with the same > versions and revisions. I take it 'port echo outdated' also gives you > nothing? Yes $ port outdated The following installed ports are outdated: gcc44 4.4.1_0 < 4.4.4_1 $ port echo outdated $ > Anything interesting shown with -d? No. > Is gcc44 inactive? No: $ port installed gcc44 The following ports are currently installed: gcc44 @4.4.1_0 (active) $ > Does 'port -v installed gcc44' or 'port -v outdated' show anything unusual? No. The gcc44 port was at version 4.4.1_0 a while ago, i.e. for at least 7 months, and as I upgrade my outdated ports about once a week this has been a problem for a while and can't be related to the switch to 1.9.0-rc1. This has started showing up as of 1.9.0-rc1, but clearly its been a problem for a while otherwise I'd be running something newer than 4.4.1_0. Is there a way the registry could have got corrupted in some strange way that would result port to think gcc44 wasn't installed? Cheers Adam _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
