Re: Getting Mauve running with Classpath+gcj/jikes+kissme

Brian, I've checked some changes into the Kissme CVS that should solve your problem. There is now a --with-gnu-classpath-build option for specifying the GNU Classpath build dir when it is different from the GNU Classpath build dir. cd ${KISSME_CVS} ./configure --prefix=${KISSME_PREFIX}

Re: Getting Mauve running with Classpath+gcj/jikes+kissme

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;

Re: Getting Mauve running with Classpath+gcj/jikes+kissme

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

Re: Getting Mauve running with Classpath+gcj/jikes+kissme

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

Re: Getting Mauve running with Classpath+gcj/jikes+kissme

Hi, On Thu, 2002-10-10 at 23:13, Mark Wielaard wrote: - Add the attached file mauve-kissme to the mauve directory. (This tells the build which tests should/shouldn't be compiled/run.) [...] At the moment you will get the following results: 158 of 6276 tests failed (Some of these are

Getting Mauve running with Classpath+gcj/jikes+kissme

Hi, Here are some instructions for getting the Mauve testsuite running with GNU Classpath+gcj/jikes+kissme. # The compiler - Get a recent gcj (= 3.2) or jikes (= 1.15) (See http://gcc.gnu.org/ or http://www.jikes.org/) # The class libraries - Get recent GNU Classpath sources from CVS.