[Cp-tools-discuss] Build succeeded, but...

[Audrius Meskauskas]

OK, the previous error can be fixed by the good kicking of the build 
system with:

address@hidden cp-tools]# gcj 
--classpath=.:/usr/share/java/bytecode.jar:/usr/share/java/asm.jar 
-fassume-compiled -I./src -I -Isrc/jars/bytecode.jar -Isrc/jars/asm.jar 
-I. -g -O2 -o localegen --main=gnu.localegen.Main 
-Dgnu.gcj.runtime.VMClassLoader.library_control=never 
src/gnu/ldml/AliasElement.o src/gnu/ldml/Analyzer.o 
src/gnu/ldml/Constants.o src/gnu/ldml/DataElement.o 
src/gnu/ldml/DetailedListElement.o src/gnu/ldml/Element.o 
src/gnu/ldml/ExpansionElement.o src/gnu/ldml/ListDataElement.o 
src/gnu/ldml/OrderedListBaseElement.o src/gnu/ldml/OrderedListElement.o 
src/gnu/ldml/ParseException.o src/gnu/ldml/Parser.o 
src/gnu/ldml/ResetElement.o src/gnu/localegen/CollationInterpreter.o 
src/gnu/localegen/JavaGenerator.o src/gnu/localegen/Main.o 
src/gnu/localegen/PropertiesGenerator.java

after error and typing "make" again, and the build goes till finish!

However only in the case when the very old ASM 1.5.3 is used. It does 
not compile with the recent 3.0 and also with any version of the 2.*.

This is also not written in INSTALL.

Conclusions:
1. We need instructions how to make the bytecode.jar. It does not appear 
automatically.
2. We need to specify the currently used versions of ASM and probably of 
KAWA also.
3. We probably need to fix the build scripts to prevent the build 
problem, described above.

Audrius.