Re: building SableVM on Cygwin

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1706043308==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigF576C45BA4BC46A973B5FAB6"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigF576C45BA4BC46A973B5FAB6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Enrico Migliore wrote:
> I built SableVM on the latest release of Cygwin without problems, and
> except for a few compilation warnings, all went well.

Nice to hear.  Yet, we should eventually get rid of these warnings.

> Now I've downloaded the sablevm-classpath trunk, I'm ready to build it
> and I've got a question:
> 
> What's the difference between the official Classpath trunk and
> sablevm-classpath one?

Not much.  Mainly, it's minor differences in what Harmony call "kernel
classes".

-- 
Etienne M. Gagnon, Ph.D.            http://www.info2.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/

--------------enigF576C45BA4BC46A973B5FAB6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEMoLTjyrJi4rH84gRAohiAJ9/yIu8ZNsoqNRl2nGU8N+b9qVs9wCeJJL7
W98BDTjN7f3E9X8bZteWmXo=
=KRfH
-----END PGP SIGNATURE-----

--------------enigF576C45BA4BC46A973B5FAB6--


--===============1706043308==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SableVM-devel mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-devel

--===============1706043308==--