Juan Antonio Martinez wrote:
El jue, 30-10-2003 a las 18:45, Dalibor Topic escribi�:
[...]
You should give us the invocation line of kjc, too. Probably ant messes up an option for kjc, and doesn't use the proper option to call it. That's an issue that using build.compiler=kjc should solve.
By echoing call to javac I obtain: .............................
[javac] javac called as:
/opt/usr/java/kaffe-1.1.2/bin/javac -d
/home/jantonio/public_html/work/test/build -classpath
/home/jantonio/public_html/work/test/build:/opt/usr/java/junit3.8.1/junit.jar:/opt/usr/java/junit3.8.1/junit/tests/runner/test.jar:/home/jantonio:/home/jantonio/public_html/work/test:/opt/usr/java/apache-ant-1.5.4/lib/xml-apis.jar:/opt/usr/java/apache-ant-1.5.4/lib/xercesImpl.jar:/opt/usr/java/apache-ant-1.5.4/lib/optional.jar:/opt/usr/java/apache-ant-1.5.4/lib/ant.jar:/ -sourcepath /home/jantonio/public_html/work/test/src -g:none -verbose /home/jantonio/public_html/work/test/src/test/Alumno.java /home/jantonio/public_html/work/test/src/test/Cuenta.java
[javac] Kjc: invalid option -- :
BUILD FAILED
file:/home/jantonio/public_html/work/test/build.xml:33: Compile failed;
see the
compiler error output for details.
...................
This is correct, so I suspect that something fails when forking ant to a new process to call the compiler. I'll try to investigate
deeper, Anyway I solved my problem :-)
I'm glad that it helped.
The problem is that kjc uses a different syntax for command line options than what ant expects, so it ends up confusing kjc. Please use build.compiler=kjc. It tells ant to use the option names required by kjc when it calls kjc.
You should also file a bug against ant's extJavac compiler binding: it should try to figure out what the external compiler is, and use the appropriate command line option conventions.
cheers, dalibor topic
_______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
