Re: FAIL format-users test

[Jim White <jim at pagesmiths dot com>]

Chris Dean wrote:
> > Works for me.  Running 'make check' using the kawa-1.7 source
> > distribution (ftp://ftp.gnu.org/pub/gnu/kawa/kawa-1.7.tar.gz) said:
>
> Hmm, both CVS and 1.7 fail for me.  Looks like I have some environmental
> issues to debug.  Any ideas?  What java version are you running?
>
> % java -version
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
> Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)

I thought that might the answer too as I was using 1.3.1 (Mac OS X 
10.2.6).

jim@CRPC37641:~/Software/kawa-1.7/gnu/xquery/testsuite> java -version
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 
1.3.1-root_1.3.1_021112-06:27)
Java HotSpot(TM) Client VM (build 1.3.1_03-69, mixed mode)

But I've now run a full clean build and check with 1.4.1 w/o any problems.

jim@CRPC37641:~/Software/kawa-1.7/gnu/xquery/testsuite> 
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Commands/java 
-version
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-39)
Java HotSpot(TM) Client VM (build 1.4.1_01-14, mixed mode)

I set that up with configure:

./configure 
JAVA=/System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Commands/java 
JAVAC=/System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Commands/javac

I would think it is some environment variable or perhaps a 
broken/customized Java installation.  Their are a bunch of environment 
variables including CLASSPATH, JAVA, JAVAC, etc.  You can seem them in 
configure:

ac_subst_vars='SHELL PATH_SEPARATOR PACKAGE_NAME PACKAGE_TARNAME 
PACKAGE_VERSION PACKAGE_STRING PACKAGE_BUGREPORT exec_prefix prefix 
program_transform_name bindir sbindir libexecdir datadir sysconfdir 
sharedstatedir localstatedir libdir includedir oldincludedir infodir 
mandir build_alias host_alias target_alias DEFS ECHO_C ECHO_N ECHO_T 
LIBS MAINTAINER_MODE_TRUE MAINTAINER_MODE_FALSE MAINT build build_cpu 
build_vendor build_os host host_cpu host_vendor host_os target 
target_cpu target_vendor target_os INSTALL_PROGRAM INSTALL_SCRIPT 
INSTALL_DATA CYGPATH_W PACKAGE VERSION ACLOCAL AUTOCONF AUTOMAKE 
AUTOHEADER MAKEINFO AMTAR install_sh STRIP ac_ct_STRIP 
INSTALL_STRIP_PROGRAM AWK SET_MAKE am__leading_dot LN_S CC CFLAGS 
LDFLAGS CPPFLAGS ac_ct_CC EXEEXT OBJEXT DEPDIR am__include am__quote 
AMDEP_TRUE AMDEP_FALSE AMDEPBACKSLASH CCDEPMODE am__fastdepCC_TRUE 
am__fastdepCC_FALSE CXX CXXFLAGS ac_ct_CXX CXXDEPMODE 
am__fastdepCXX_TRUE am__fastdepCXX_FALSE GCJ ac_ct_GCJ GCJFLAGS EGREP 
ECHO RANLIB ac_ct_RANLIB CPP CXXCPP F77 FFLAGS ac_ct_F77 LIBTOOL 
GCJDEPMODE am__fastdepGCJ_TRUE am__fastdepGCJ_FALSE LIBTOOL_DEPS 
WITH_GCJ_TRUE WITH_GCJ_FALSE ENABLE_XML_TRUE ENABLE_XML_FALSE 
ENABLE_SERVLET_TRUE ENABLE_SERVLET_FALSE WITH_SWING_TRUE 
WITH_SWING_FALSE WITH_AWT_TRUE WITH_AWT_FALSE WITH_SAX2_TRUE 
WITH_SAX2_FALSE ENABLE_KAWA_FRONTEND_TRUE ENABLE_KAWA_FRONTEND_FALSE 
pathsep filesep JAVA JAVAC XML_SELECTED AWT_SELECTED SWING_SELECTED 
GCJ_COMPILED_SELECTED GCJ_SELECTED extra_java TOP_BUILDDIR 
JEMACS_VERSION LIBOBJS LTLIBOBJS'

If you use Ant (which I assume you aren't because it doesn't run the 
tests), then ANT_HOME and JAVA_HOME become relavent.

AFAICT, the only variable that matters I'm using are PATH.

Although I use XSLT a fair bit, I haven't used Kawa's so I don't know 
what might be affecting it.  I don't think it uses Xalan, but if it did 
then it would be easy to get things mixed up with the various versions 
and the changes from JDK 1.3 to 1.4.

Jim
--
"I love deadlines. I love the whooshing sound they make as they fly by." 
-- Douglas Adams