Re: [Sablevm-developer] Code indenter / Uncompilable classes

[<eg...@j-...>]

Hi Ian,

On Fri, Aug 31, 2001 at 05:43:24PM +0000, Ian Rogers wrote:
> files I'm running "find src -name '*.java'|xargs jikes +E -classpath
> /home/ian/sable/sablepath-classes/src:/home/ian/old-classpath". Jikes
> version 1.2. The story so far:

I have tried recompiling jikes 1.14 from sources, but it didn't solve the
segmentation fault problem.  I have noticed that there's a bug report
on the Debian package I was using, relatively to this problem, so 
I grabbed the sources from :

http://oss.software.ibm.com/developerworks/project/showfiles.php?group_id=10

The problem is that jikes 1.02 is not available there.  Do you have a copy
of this packages (sources)?

> The jar stuff relies on java/util/zip which for some reason isn't in the
> classpath repository. If it were I'm confident this would build.

I've noticed your request on the classpath-list.  Hopefully people will finally
check-in those sources.

> > src/java/net/URLClassLoader.java
> 
> Built fine for me. Possible issues with the Jar stuff tho'.

I need to get a version of jikes that does not sigfaults.  Maybe it is
related to the fact I have GNU LibC 2.2.4 on my system?

> I'm running a slightly older version of Jikes and things appear to be
> fine. I'm keen to keep using this older version of Jikes too, until
> someone points out a really good reason to upgrade.

My problem is that I'm on Debian "unstable" which keeps updating to the latest
"stable" version of programs (which means 1.14 for Jikes)...  I can always do
a local installation, out of source packages too, but I didn't find version 1.02.

I'll try the oldest one available 1.04 and report back success/failure.

> In summary, everything is there and building except Swing and the Jar
> related stuff. As some of the core stuff relies on the Jar stuff I'm
> keen we get that working. I'll e-mail the maintainer and hopefully find
> out when the stuff will appear in the classpath CVS repository. The
> Swing stuff isn't critical to me, and it appears very incomplete. I
> suggest we move it out of the code tree for the time being.
> 
> Finally, the way I'm building the code at the moment puts all the
> pressure on jikes. Should we build a set of makefiles, configure, etc..
> ?


The "build.xml" file is the equivalent of Makefile.am/configure.ac files.
It is for use with the Jakarta "ant" tool.

See http://jakarta.apache.org/ant/

This tool is written in Java, and offers a much more appropriate way to
build classes, jar files, and distributions for Java programs than
the GNU auto-tools.  It has a pretty simple "XML" based syntax.

We can use it to "exclude" from compilation those files we know not to build.

My problem was that, on my system, jikes failed to compile too many classes.

Currently, I use Sun's jdk to "run ant".  Hopefully, someday soon I'll be able
to run it on SableVM instead.  Obviously, we will also need to provide
a simple script to bootstrap the first compilation on a user system;-)

But for maintenance, ant is a charm to use (for the Java part).

Obviously, we want to maintain the JNI/C code under the GNU auto* tools.  This
is why I have made a separate sablepath-lib CVS project for it.

You could give Ant a look and ask me any question you have.

I'll get back as soon as I can get jikes to work decently on my system.

If you have made any modifications to the sources, you can check-them in CVS.
If you have Ant running, you can add an "exclude" specification in the <javac ...>
task so to exclude the files you "moved away" in your local copy.

Have fun!

Etienne
-- 
Etienne M. Gagnon                                    eg...@j-...
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/