On 01/06/2010 04:59, xiaofen...@iscas.ac.cn wrote:
> The config.log is lke follows:
> I extract the lines that are related to ant, here it is
> -------------------------------------------
> PATH: /cygdrive/c/ant/bin
> .....
> 
> configure:28329: checking for jakarta-ant
> configure:28362: result: no
> configure:28329: checking for ant
> configure:28347: found /cygdrive/c/ant/bin/ant
> configure:28359: result: /cygdrive/c/ant/bin/ant
> configure:28452: checking whether ant is >= 1.6.0
> configure: ant_version tools.jar.
> 1.8.0
> configure: ant_version_major tools
> configure: ant_version_minor jar
> configure:28467: error: no, you need at least ant >= 1.6.0
> .....
> 
> ac_cv_path_ANT=/cygdrive/c/ant/bin/ant
> .....

i've got an idea how that could happen...
on a Ubuntu 10.04 system:

> ant -version
Unable to locate tools.jar. Expected to find it in 
/usr/lib/jvm/java-6-openjdk/lib/tools.jar
Apache Ant version 1.7.1 compiled on March 5 2010

> JAVA_HOME='/usr/lib/jvm/java-6-sun' ant -version
Apache Ant version 1.7.1 compiled on March 5 2010

so if ant is somehow unhappy it will print extra junk on stdout.
the test in configure.in does not expect that.
apparently JAVA_HOME is set up before the ant test in configure.in.

xiaofeng08, what does config.log say about JAVA_HOME?

Rene, any idea how to prevent this?
maybe a grep for "version" in the check would help?

-- 
"I believe OS/2 is destined to be the most important operating system,
 and possibly program, of all time." -- Bill Gates, 1987


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Reply via email to