Chip Salzenberg via RT wrote:
Is this bug still reproducible this even after removing everything
Parrot-related from /usr/local? (Also /usr/bin and /usr/lib if you
happen to have installed e.g. Debian's parrot packages.)
I deleted /usr/local/{bin,doc,include,lib}/parrot (or something very
clo
Is this bug still reproducible this even after removing everything
Parrot-related from /usr/local? (Also /usr/bin and /usr/lib if you
happen to have installed e.g. Debian's parrot packages.)
On Jun 21, 2006, at 11:16, [EMAIL PROTECTED] (via RT) wrote:
Invoking Parrot to generate runtime/parrot/include/config.fpmc --cross
your fingers
./miniparrot config_lib.pasm > runtime/parrot/include/config.fpmc
Sounds like the still existing problem of an installed parrot
interfering with b
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #39552]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39552 >
---
osname= freebsd
osvers= 6.0-stable
arch= i386-freebsd-64int
cc= cc
---
