Mark is correct. If the pcre-config program cannot be found, then
this is the condition you should expect.
Note that libpcre does not come with OSX, so this is not unusual (I
have it installed via Fink).
Devin
On Dec 20, 2007 8:48 AM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> That output sugges
That output suggests that you dont have libpcre installed, which makes
it not much of a test for the patch. :)
On 12/19/07, James Keenan via RT <[EMAIL PROTECTED]> wrote:
> On Mon Dec 03 20:04:08 2007, [EMAIL PROTECTED] wrote:
> > Uploading updated version of patch based on discussion with chroma
On Sunday 02 December 2007 21:21:49 Devin Heitmueller wrote:
> 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.
Oh. I missed that, but it makes se
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
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
