public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Raif S. Naffah" <raif@fl.net.au>
To: jikesrvm-researchers@www-124.ibm.com,
	David P Grove <groved@us.ibm.com>,
	jikesrvm-researchers@oss.software.ibm.com
Cc: GNU Classpath <classpath@gnu.org>,
	Mauve <mauve-discuss@sources.redhat.com>
Subject: Re: [Jikesrvm-researchers] running Mauve with JikesRVM(+GNU Classpath)
Date: Mon, 07 Apr 2003 11:57:00 -0000	[thread overview]
Message-ID: <200304072157.57044.raif@fl.net.au> (raw)
In-Reply-To: <OF793DCEED.0F41FF88-ON85256D01.003EB57B-85256D01.00401C37@us.ibm.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

hello David,

On Mon, 7 Apr 2003 09:41 pm, David P Grove wrote:
> Hi,
>
>         I usually do the following for your step 3 (assuming you want
> to test the glib.zip in the JikesRVM build directory. BTW, for
> historical reasons glib.zip is copied into the build directory and
> renamed to rvmrt.jar by the JikesRVM build process).
>
> $ JAVAC="$RVM_BUILD/jbuild.tool" \
>   JAVA="rvm -X:h=100" \
>   ../mauve/configure
>
> jbuild.tool is a script that invokes jikes passing it a bootclasspath
> that includes all the .jar and .classes of the Jikes RVM build
> directory. Jikes RVM's classpath includes the jar files in the build
> directory automatically, so you don't have to specify that.

thanks a bunch :-)

cheers;
rsn


> --dave
>
> "Raif S. Naffah" <raif@fl.net.au>
> Sent by: jikesrvm-researchers-admin@www-124.southbury.usf.ibm.com
> 04/06/2003 08:56 PM
> Please respond to jikesrvm-researchers
>
>         To:     GNU Classpath <classpath@gnu.org>, JikesRVM
> <jikesrvm-researchers@www-124.southbury.usf.ibm.com>, Mauve
> <mauve-discuss@sources.redhat.com>
>         cc:
>         Subject:        [Jikesrvm-researchers] running Mauve with
> JikesRVM(+GNU Classpath)
>
>
> hello there,
>
> if somebody is using the above combo to test GNU Classpath and
> security classes, can they confirm this (how-to-do):
>
> 1. build JikesRVM.  which may download the Classpath CVS HEADs.
> 2. cd to the MAUVE test directory; eg. .../mauve-test
> 3. do:
> $ JAVAC="jikes -bootclasspath <path/to/glibj.zip>" \
>   JAVA="rvm
> -X:vmClasses=<path/to/glibj.zip>:<$RVM_BUILD/RVM.classes>" \
> ../mauve/configure
>
> (unless there's an easier way)
>
> 4. do:
> $rm -rf .save-keys choices ; \
>   make check KEYS="security" TESTFLAGS="-verbose -debug"
>
> where a mauve-security contains something like:
>
> JDK1.0
> JDK1.1
> JDK1.2
> JDK1.3
> JDK1.4
>
> !java.applet
> !java.awt
> !java.beans
> !java.io
> !java.lang
> !java.math
> !java.net
> !java.nio
> !java.rmi
> java.security
> !java.sql
> !java.text
> !java.util
>
> !javax.
>
> 5. the result should be (as of today):
>    0 of 164 tests failed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE+kWfA+e1AKnsTRiERA4+1AJ9dtUUwqUtVNokNj8E8Ntb2gx6KwgCg8Gao
uYxeTt7f/kZNOIB8kbPayNU=
=asiF
-----END PGP SIGNATURE-----

       reply	other threads:[~2003-04-07 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF793DCEED.0F41FF88-ON85256D01.003EB57B-85256D01.00401C37@us.ibm.com>
2003-04-07 11:57 ` Raif S. Naffah [this message]
     [not found] <OF32039E15.A32F208C-ON85256D01.00078BA3-85256D01.0007D0D4@us.ibm.com>
2003-04-07  2:10 ` Raif S. Naffah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304072157.57044.raif@fl.net.au \
    --to=raif@fl.net.au \
    --cc=classpath@gnu.org \
    --cc=groved@us.ibm.com \
    --cc=jikesrvm-researchers@oss.software.ibm.com \
    --cc=jikesrvm-researchers@www-124.ibm.com \
    --cc=mauve-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).