Re: SableVM SDK - General Info and Gentoo Update

On Sun, 2005-29-05 at 16:02 -0400, David Bélanger wrote:
> Hi,
> 
> I completed a Gentoo ebuild (package build script) that builds
> everything for SDK 1.12_pre2 and everything seems to work though
> not tested a lot.

Great, thanks!

> Things of general interests to non-Gentoo people:
> 
> assert patch: removes assert statements allowing builds on pre-SDK-1.5.

Weird.  Is your version of jikes recent enough?  Did you try
--with-jikes=internal ?  I've not noticed any problems.  And assert IIRC
was introduced somewere in 1.3.

> bootstrap patch: ensure that SableVM SDK is used to build cp-tools,
> gjdoc, etc. by setting JAVAC, JAR, JAVA env variables.  Ideally, we
> might want to have configure options to control this.  On Gentoo
> systems, JAVAC (and a few others) variable are defined to the current VM
> SDK selected.  Therefore, cp-tools/gjdoc etc. are build with currently
> selected system VM instead of SableVM SDK.

Maybe we should just unset JAVAC/JAR/JAVA in Makefiles, like it's done
with MAKEFLAGS?

> I think it should default to SableVM SDK unless otherwise specified with
> configure flags i.e. the SableVM SDK should always bootstrap itself.
> I don't think it should rely on pre-set environment variables as it
> is currently the case.

The idea was that if there's no installation of jikes or fastjar found
(NOT: javac/jar!) then they will be built and installed.  But if they
are found then these already installed ones should be used.

> chmod patch: fixes earlier bug reported.  When autoconf tools rerun and
> recreate files - permissions were not always set for BUILDIR/bin.

Hope it's commited now.

> dir patch: One way to fix DESTDIR bugs (undo Greg's Makefile.am changes
> and uses config options).  An alternative way is to keep Greg's changes
> and remove DESTDIR from all bindir,libdir,...

My mistake IIRC.  I thought the DESTDIR was missing, so I added it, but
apparently it was all right.  So undoing my change seems like the right
thing to do.

> Note: fastjar will not rebuild automatically Makefile.in if Makefile.am
> is built unlike all other code.  By adding the config switch:
> --enable-maintainer-mode
> to fastjar, it will make the build dep behaviour ok like the others.
> This should not affect end users but is a little bit confusing to dev
> when they patch Makefile.am and expect Makefile.in to be regenerated
> like the others. :)

IIRC we could either remove the MAINTAINER_MODE macro from configure or
add --enable-maintainer-mode to the flags passed to fastjar's configure
(you can do that in top-level configure).  I am unsure what's the
benefit from using MAINTAINER_MODE anyway, but it might be just my lack
of knowledge on that topic.

Thanks & cheers,

			Grzegorz B. Prokopski

PS: I'll be way less visible until the end of June as I need to study
for an important examination.  I should still be reading the ML, but
dont wait for my 'ok' when fixing bugs.
-- 
Grzegorz B. Prokopski           <[email protected]>
SableVM - Free, LGPL'ed Java VM  http://sablevm.org
Why SableVM ?!?                  http://sablevm.org/wiki/Features
Debian GNU/Linux - the Free OS   http://www.debian.org