On Thu, Jun 11, 2009 at 01:11:22AM -0500, Ryan Schmidt said: > On Jun 11, 2009, at 00:43, Bryan Blackburn wrote: [...] >> >> Does anyone know why cyrus-sasl2 has that pre-configure check? I found >> tickets #17158 and #17328, the former being the one which added it but >> with >> no description of why. Having just commented-out the pre-configure >> bit, >> upgrading from 2.1.22 to 2.1.23 worked just fine. Is it >> OS-version-specific, arch-specific, or MacPorts-version-specific? > > I also have no problem upgrading from 2.1.22 to 2.1.23, on Mac OS X > 10.4.11 Intel with Xcode 2.5 and MacPorts 1.7.1. > > But if you downgrade your cyrus-sasl2 to 2.1.21 first, then try to > upgrade, you should get the failure I got (see below).
Ah, so the secret is to come from the .21 version...okay I've attached a patch to ticket #17328 which should deal with this. The patch is a bit kludgy but without messing around with the autoconf stuff (which is pretty old), this is the simplest way to deal with it. Bryan [...] _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users