In order to insert the $pcre_libpath into the content of the PIR, I had to change the interpolation mode in pir_output_is(). This therefore required me to escape the backslashes in the heredoc.
If there's a more preferred approach to this sort of problem, let me know and I will happy resubmit the patch with said approach. Devin On Dec 3, 2007 12:17 AM, chromatic <[EMAIL PROTECTED]> wrote: > On Sunday 02 December 2007 21:04:28 Devin Heitmueller wrote: > > > The attached patch will address a parrot test failure in the PCRE > > module (t/library/pcre.t) in the case where the libpcre library is > > installed in a nonstandard location. > > > > In my case, it occurs on OS X that Fink installed libpcre into > > /sw/lib, and so the test believes that PCRE is installed because the > > pcre-config utility returned zero, but it cannot find the library. > > > > The change runs pcre-config to get the location of the library, and > > then updates the PARROT_LIB_PATH_DYNEXT to contain the additional > > entry. > > Everything looks reasonable except the double-escaped newline; is this an > artifact of the patch? > > -- c > -- Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller
