On Sun, Aug 13, 2006 at 11:28:03PM +0200, Yann Dirson wrote:
> The problem is more subtle, as shown by the arm build of 2.8a-2:

>    java: no
> *** ERROR:configure:Can't configure Java.
> Command:
> ./autoconf/javatest --java=/usr/bin/java --jflags= --jvflags=-noverify 
> --javac=/usr/bin/javac --jcflags=-O --user=buildd --tmp=/tmp --cpsep=":"
> failed unexpectedly (see configure.log for details).

> That is, it is indeed checking for an available /usr/bin/java... which
> we have, because gij is installed by side-effect.  But then, what is
> this failure on arm ?

Sorry, this seems to be something quite different from the bug I was
originally reporting on; I have no idea why these build scripts aren't able
to find a working java on the buildd.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to