[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Crypto] [bug] configure in CVS doesn't seem to have the executa
From: |
Raif S. Naffah |
Subject: |
Re: [GNU Crypto] [bug] configure in CVS doesn't seem to have the executable bit set |
Date: |
Mon, 1 Dec 2003 04:42:29 +1100 |
User-agent: |
KMail/1.5 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
hello Dalibor,
On Mon, 1 Dec 2003 04:35 am, Dalibor Topic wrote:
> ...
> The autogen.sh script breaks now because it can't run jikes. That's
> O.K., as I want to build the library using kjc anyway. But I can't
> get that to work.:
>
> bash-2.05a$ ./autogen.sh --with-jikes=/tmp/topic/current-jit3/bin/kjc
> *** Info: Generating GNU build toolchain scripts and files for GNU
> Crypto. aclocal -I .
> automake --add-missing --copy
> autoconf
> ./configure --enable-maintainer-mode
> --with-jikes=/tmp/topic/current-jit3/bin/kjc
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... /usr/bin/gawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of
> Makefiles... yes You have CLASSPATH ., hope it is correct
> checking for gcj... no
> checking for guavac... no
> checking for jikes... jikes
> checking if jikes works... configure: error: The Java compiler jikes
> failed (see config.log, check the CLASSPATH?)
> *** Info: Done. Type 'make' to compile GNU Crypto.
>
> where the log file says:
>
> configure:1772: checking for jikes
> configure:1788: found /HG/hiwis/topic/jikes/bin/jikes
> configure:1798: result: jikes
> configure:1855: checking if jikes works
> configure:1869: jikes Test.java
>
> Found 1 system error:
>
> *** Semantic Error: You need to modify your classpath, sourcepath,
> bootclasspath, and/or extdirs setup. Package "java/lang" could not be
> found in:
> .
> .
>
> configure:1872: $? = 1
> configure:1876: error: The Java compiler jikes failed (see
> config.log, check the CLASSPATH?)
>
> so it seems to be picking the wrong compiler.
indeed. i'm looking into it and will let you know soon how to work
around this.
cheers;
rsn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Que du magnifique
iD8DBQE/yiwF+e1AKnsTRiERA4xVAJ9jAuxQ8/eH6W68/QJg2vwwBAkPzgCfbrPk
N8szyTL5AqG5/l2CDATZMDU=
=erQN
-----END PGP SIGNATURE-----