ryandesign at macports.org
Fri Apr 4 16:01:34 PDT 2014
> 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:
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.
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:
More information about the macports-dev