<div dir="ltr">On Wed, Jul 15, 2015 at 8:54 PM, Ryan Schmidt <span dir="ltr"><<a href="mailto:ryandesign@macports.org" target="_blank">ryandesign@macports.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
> On Jul 15, 2015, at 4:53 PM, <a href="mailto:eborisch@macports.org">eborisch@macports.org</a> wrote:<br>> +configure.env-append INTLTOOL_PERL=${prefix}/bin/perl5.22<br>
<br>
I guess this port uses intltool? So it should really have a build dependency on intltool, not p5.22-xml-parser.<br>
<br>
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.<br></blockquote><div><br></div><div>Passes in trace mode; looking at what happens, it has its own <a href="http://intltool-merge.in">intltool-merge.in</a> that gets updated with INTLTOOL_PERL at configure time on its shebang line. Buildbots also all completed without error.</div><div><br></div><div>So -- thanks for the catch, but I think we're ok on this one.</div><div><br></div><div> - Eric</div></div></div></div>