Mark Wielaard <[EMAIL PROTECTED]> writes: > Hi, > > On Sat, 2002-10-19 at 02:14, Brian Jones wrote: > > Mark Wielaard <[EMAIL PROTECTED]> writes: > > > > > # The runtime > > > - Get recent Kissme sources from CVS (or maybe a recent build). > > > (See http://kissme.sourceforge.net/) > > > - Do the magic auto* dance (note the -a for automake): > > > aclocal; autoheader; automake -a; autoconf > > > - ./configure --enable-use-zips --with-gnu-classpath=/path/to/src/classpath > > > > This didn't work for me, _KISSME_TEST_CLASSPATH_DIR checks for > > $1/kissme/vm/loaoders/JarClassLoader.{java,class} and classpath has > > neither. Also specifying the source directory will not let it find > > java/lang/Class.java, this is in vm/reference/... instead, so I don't > > get the test for the kissme class loader or I'd use the > > kcp_status=binary. > > Those classes can be found in the kissme/classes directory which > configure should find. > > Note that I configured kissme inside the source dir, maybe it doesn't > configure well when configuring from a different dir?
cd "${KISSME_CVS}" && ./configure --prefix=${KISSME_PREFIX}
--enable-use-zips --with-gnu-classpath=${CLASSPATH_CVS}/build
--with-classpath-install-dir=${CLASSPATH_PREFIX} >> ${LOG} 2>&1
I always configure classpath in a separate build directory. Maybe it
doesn't like that. I did change to configuring kissme in
${top_srcdir} but that didn't help.
checking Kissme Classpath directory... not found
checking /home/cbj/mauve/classpath/build... no
configure: error: Cannot find the selected GNU Classpath build directory
(/home/cbj/mauve/classpath/build).
Brian
--
Brian Jones <[EMAIL PROTECTED]>
kissme-mauve
Description: Binary data
