/trunk/mail/configure & JAF

configure scripts fails to recognize when JAF is provided by the JDK/JRE.

The JAF 1.1.1 page cited below states Java SE 6 includes JAF.

What is involved in revision configure script to probe the JDK/JRE?

Conrad Pino

----------------------------------------------------

JAF 1.1.1:
http://www.oracle.com/technetwork/java/javase/downloads/index-135046.html

JAF 1.0.2: http://www.oracle.com/technetwork/java/javase/jaf-136260.html

----------------------------------------------------
[conrad@ceos mail]$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/home/conrad/gnu/svn/trunk/mail/missing: Unknown `--is-lightweight' option
Try `/home/conrad/gnu/svn/trunk/mail/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcj... gcj -C
checking if gcj -C works... yes
configure: WARNING:
The build seems to be using gcj for bytecode generation.  Some
versions of gcj are known to produce bad bytecode.  See here for a
list of bugs that may be relevant:

http://gcc.gnu.org/bugzilla/buglist.cgi?component=java&keywords=wrong-code&o
rder=default

At least bug 19921 is known to affect gjdoc (in Feb 2005).

You may want to set the environment variable JAVAC to an alternate
compiler, such as jikes, to make sure that you end up with valid
bytecode.

checking for gjdoc... gjdoc
checking for fastjar... fastjar
checking for activation.jar... not found
configure: error: can't find activation.jar; use --with-activation-jar
[conrad@ceos mail]$ ./configure --with-activation-jar
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/home/conrad/gnu/svn/trunk/mail/missing: Unknown `--is-lightweight' option
Try `/home/conrad/gnu/svn/trunk/mail/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcj... gcj -C
checking if gcj -C works... yes
configure: WARNING:
The build seems to be using gcj for bytecode generation.  Some
versions of gcj are known to produce bad bytecode.  See here for a
list of bugs that may be relevant:

http://gcc.gnu.org/bugzilla/buglist.cgi?component=java&keywords=wrong-code&o
rder=default

At least bug 19921 is known to affect gjdoc (in Feb 2005).

You may want to set the environment variable JAVAC to an alternate
compiler, such as jikes, to make sure that you end up with valid
bytecode.

checking for gjdoc... gjdoc
checking for fastjar... fastjar
checking for yes/activation.jar... configure: error: can't find
activation.jar in specified path
[conrad@ceos mail]$ javac -version
javac 1.6.0_30
[conrad@ceos mail]$