Re: Release [was: Re: [Sablevm-developer] Alpha inlined threading works now, but...]

[Prof. E. M. G. <eti...@uq...>]

On Wed, Feb 19, 2003 at 07:22:04PM +0100, Grzegorz B. Prokopski wrote:
> Could you please merge attached bits too?
>=20
> I'd like to ask about possible new release features and timeframe.
> If you had enough resources, I'd love to see there:
> - merge of reflection stuff (already done FWICS)
> - merge of PPC sutff (already done FWICS)
> - merge of alpha stuff

I'm working on this right now.

> - update to new gnu classpath release

I was planning to instead get the SableVM native/class library stuff
into official Classpath CVS, instead of continuing to manage a vendor
branch.  But this might involve some political discussions on the
Classpath ML first, as I'd like them to use indentation tools as I do
in sablevm-*-library, which makes it so simpler to read and maintain
code written by others.  It could also affect the build process and
directory layout...

> As I'd like to get new release with _fixes_ ASAP - I think the last
> thing could be postponed for later time.
> Not that I want to push you to do sth, but can you release today? ;-)

This is what I am working on.

> <reminder mode=3Dwhining>
> It's of course fun to play with portability etc., but I'd like to
> bring back the fact that for the people it's still hard to use
> SableVM because... free java packages are getting compiled with
> newer jikes which makes them unusable with current SableVM.
>=20
> That way - even having the reflection stuff in place - it may
> be impossible to run prepackaged ANT for example. :-(
> </reminder>

I know.  If I could only increase the number of hours to 25 hours per
day;-)

Maybe you could get the jikes maintainer to add a jikes1.15 package in
unstable.  I already tried, but I think he does not like the idea.

> PS: Do you have any suggestions for IA64 problems? (or at least why am
> I unable to setup brakpoint by name.c:xx?) It's a pity to make no use
> of a machine which is dedicated to get SableVM working.

Are you compiling SableVM using your .deb specific build process, or
are you using the build-many script?  I see no reason for the
build-many script not to spit out debuggable code (for sablevm-debug).

If you use your own build process, make sure ** not to call ** "make
clean" betweem "make install" and "gdb sablevm", as many SableVM
source files are automatically generated, and are deleted by "make
clean".

Etienne

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