chromatic wrote:
I vote for fixing the buggy test (no pcre, no reason to run the tests) but not
working around standard dynamic library loading.
It is not that easy (I think). Also, I do not know much about these
things, so let me try explain some more details.
1) the configure step finds
On Thu, May 01, 2008 at 12:19:06PM -0700, chromatic wrote:
> I'm not sure. Why add special logic to Parrot to find poorly-installed
> libraries? If you install a dynamic library outside of your normal system
> library paths, no other program will find it. If you want other things to
> find it
On Thursday 01 May 2008 12:07:47 Alberto Simões wrote:
> There was a test (test three from t/examples/library.t) that was failing
> and failing under MacOS X. That test relies on libpcre that is not
> available by default on MacOS X.
It seems to me that the test should skip itself if dynamic load
Hi, Folks
I am kind of 'out' from Parrot for a long time, and probably there is
something that I am missing.
There was a test (test three from t/examples/library.t) that was failing
and failing under MacOS X. That test relies on libpcre that is not
available by default on MacOS X.
If you u
