Well it fixed part of the parrot problem... Now I get a syntax error
for tcl.pir, line 18, unexpected dot, so I'm guessing that .DynLexPad
isn't set. I guess the little comment at the top, "therefore the
.DynLexPad constant is already available" isn't quite true.
Joshua
On Jan 13, 2006, at 2:27 PM, Jonathan Worthington via RT wrote:
"Joshua Isom (via RT)" <[EMAIL PROTECTED]> wrote:
Recently we stopped linking extend.obj into dynclasses. The meaning
behind
this is that functions in extend.c should not be used in dynclasses;
leo
explained on IRC that "these functions are just wrappers around
existing
other APIs and shouldn't be used inside Parrot code".
Parrot_PMC_typenum has already been removed, thus why you got undefined
symbols warning - the symbol doesn't exist any more. I've just ci'd
changes
to the tcl PMCs not to use Parrot_PMC_typenum and Parrot_call_sub, and
they
now build again here (and should elsewhere). (Note to Coke/mdiep:
hope I
fixed it right...)
If you could verify that it now builds on darwin, this can be closed
up.
Thanks,
Jonathan
