"Larry Wall" <[EMAIL PROTECTED]> wrote:
I just had the same problem, and chased it down to the fact that it was
using -L/usr/local/lib ahead of its own blib, so it was linking against
an old libparrot of some sort or other. I'm not sure what the correct
solution is, but as a workaround I deleted /usr/local/lib/libparrot*
and then it links.
Ooh, nice catch - I'm to blame for the addition of those two functions but
(a) develop on Win32 where this likely wouldn't show up and (b) don't have
an installed Parrot anyway, thus meaning I've had a rather hard time trying
to find the problem. ;-)
Solution may be to have the full path to libparrot in the link line, to
ensure we get the right one. Thoughts, anyone?
Thanks,
Jonathan
