cyrus-sasl2 upgrading (was Re: subversion on 10.4)
ryandesign at macports.org
Wed Jun 10 23:11:22 PDT 2009
On Jun 11, 2009, at 00:43, Bryan Blackburn wrote:
> On Wed, Jun 10, 2009 at 11:54:59PM -0500, Ryan Schmidt said:
>> I see the same symptom, yes. A similar solution would need to be
>> to the cyrus-sasl2 port. If you can come up with a general change
>> should be made to MacPorts base that will not adversely affect too
>> other ports, we can certainly consider it.
> Does anyone know why cyrus-sasl2 has that pre-configure check? I
> 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
> 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).
Presumably the ABI changed between 2.1.21 and 2.1.22 but not between
2.1.22 and 2.1.23, and as we see it's trying to link with the already-
installed older version of the libraries before trying to use the
newer ones it just build (-L/opt/local/lib appears in the link
command before -L../lib/.libs).
/bin/sh ../libtool --mode=link /usr/bin/gcc-4.0 -Wall -W -O2 -L/opt/
local/lib -L/opt/local/lib -o pluginviewer pluginviewer.o ../lib/
libsasl2.la -lresolv -lresolv -lpam
/usr/bin/gcc-4.0 -Wall -W -O2 -L/opt/local/lib -L/opt/local/lib -
o .libs/pluginviewer pluginviewer.o -L../lib/.libs -lsasl2 -ldl -
lresolv -lresolv -lpam -lresolv -lresolv -lpam
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
collect2: ld returned 1 exit status
make: *** [pluginviewer] Error 1
make: *** [all-recursive] Error 1
make: *** [all] Error 2
More information about the macports-users