[118533] trunk/dports/net/pidgin/Portfile

David Evans devans at macports.org
Fri Apr 4 16:54:51 PDT 2014

On 4/4/14 4:01 PM, Ryan Schmidt wrote:
>> On 4/4/14 1:22 AM, Ryan Schmidt wrote:
>>> You should use a specific version of perl instead, like perl5.16.
> Maybe I take that back, because:
> On Apr 4, 2014, at 07:44, Eric Gallager wrote:
>> I thought we were doing variants now, when the dependency is for more
>> than just the "perl" executable, at least:
>> https://trac.macports.org/ticket/43193
> In this case, the dependency isn’t for more than just the perl executable, is it? The port does build and install perl modules, but it installs them in a pidgin-specific location, not in the versioned directory for whatever version of perl it found. And it doesn’t appear that the path to perl gets baked into any installed files. So maybe the perl version doesn’t matter after all.
Mostly true with the exception of the baked-in part.  The port builds


which has a binary dependency on the versioned libperl.dylib that
belongs to the perl it configured with.

In my mixed versioned test case this is perl5.12

otool -L /opt/local/lib/purple-2/perl.so

/opt/local/lib/perl5/5.12.4/darwin-thread-multi-2level/CORE/libperl.dylib (compatibility
version 5.12.0, current version 5.12.4)

This is caused by this line in configure.ac:

PERL_LIBS=`$perlpath -MExtUtils::Embed -e ldopts 2>/dev/null |$sedpath
's/-lgdbm //'`

On Apr 4, 2014, at 10:59,

David Evans wrote:
>> Unfortunately that doesn't work in this situation.  configure.ac needs
>> to be modified to respect
>> configure.perl before a version specific perl can be used.
>> configure.ac uses this code to test for perl:
>>        AC_PATH_PROG(perlpath, perl)
>>        AC_MSG_CHECKING(for Perl compile flags)
>>        PERL_CFLAGS=`$perlpath -MExtUtils::Embed -e ccopts 2>/dev/null`
> I’ve changed my mind about the necessity of this, but if we did want to use a specific perl, patching the configure file would not be necessary; you can just add this to configure.args:
> ac_cv_path_perlpath=${prefix}/bin/perl5.16
Yes, this works (just tried it on a test build).

Actually, if I were the maintainer of this port, I'd put perl, tcl and
tk in variants as I'm not sure how much demand
there is for these bindings to libpurple and installing them in pidgin's
own tree makes them inconvenient to use.

Unfortunately, the maintainer has been AWOL for some time so it's
cumbersome to make changes.

More information about the macports-dev mailing list