On Sunday 10 October 2004 21:50, Jeff Clites wrote:
> Did you run 'make' again after running the "c++ -o parrot..." line
> below? If not, I bet the problem is just the stuff in
> runtime/parrot/include never got bytecode-compiled, because the stuff
> at the end of the make process never ran.
Ah yes, this is indeed a good explanation for the test failures.
I think we should add a test that checks if all generated files were build 
correctly.

I've disabled the code that removes -licudata, I hope it works now.
Sorry for that!

> JEff
jens

Reply via email to