William Coleda <[EMAIL PROTECTED]> wrote:After some distractions I got back to this today.
After doing the merge and resolving all the conflicts (of which there really weren't that many), I get it to build, and then get a:
Great. So 0.1.2 will be delayed until its in?
You're the the pumpking - that's your call, not mine.
I'll keep poking at it. Looks like a bootstrapping problem on string initialization.
Are the encoding_init() / chartype_init() lines enabled in
string.c:string_init()?
leo
No, they weren't. Of course, if I enable them, I get "undefined symbols" during the link phase... a grep through the source doesn't seem to have them defined anywhere. (in the main branch or the integration I'm trying).
Not that it should matter. the backtrace from gdb shows the error occuring earlier in string_init than the encoding_init line. The problem is in the prefix=Parrot_get_runtime_prefix line... which eventually tries to call CHARSET_GET_CODEPOINT on a string with what seems to be a null encoding.
Regards.
