On Wed, Jul 15, 2015 at 8:54 PM, Ryan Schmidt <[email protected]> wrote:
> > > On Jul 15, 2015, at 4:53 PM, [email protected] wrote: > > +configure.env-append INTLTOOL_PERL=${prefix}/bin/perl5.22 > > I guess this port uses intltool? So it should really have a build > dependency on intltool, not p5.22-xml-parser. > > The problem is you don't know for what version of perl the user has > installed intltool -- you don't know what variant of the intltool port the > user has used. So instead of setting INTLTOOL_PERL, our preferred way of > dealing with this issue is to autoreconf, which will regenerate the > configure script using our patched copy of intltool.m4 installed by the > intltool port, which no longer uses the INTLTOOL_PERL environment variable. > Passes in trace mode; looking at what happens, it has its own intltool-merge.in that gets updated with INTLTOOL_PERL at configure time on its shebang line. Buildbots also all completed without error. So -- thanks for the catch, but I think we're ok on this one. - Eric
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
