Re: sablevm-sdk-1.12
Peter Lovell <[email protected]> Wed, 13 Jul 2005 14:29:00 -0400
| Newsgroups | gmane.comp.java.vm.sablevm.general |
|---|---|
| Message-ID | <[email protected]> |
On Jul 13, 2005, at 1:50 PM, Peter Lovell wrote: > HI, > I've been testing sablevm-sdk-1.12 and have a couple of comments. I > can enter bugzillas with details for those which need it. > > Building on Linux (SuSE 9.1 pro) > 1. after configure/make/make install it doesn't seem to pick up the > library path. I had thought that the path was known to the > executable and did not need a run-time-path specification. Putting / > usr/local/lib in LD_LIBRARY_PATH makes it work, but something's not > right. > > 2. I don't have antlr.jar on the system so gjdoc would not build. I > thought that configure sensed this and would disable gjdoc, but it > didn't. I reconfigured with --disable-gjdoc and the build worked. > > 3. I didn't specify a "jikes" so the build used the existing one > and fell over (was version 1.19, which is too old). It might be > nice if configure can test and switch to "internal" of the existing > one isn't suitable > > > On Mac OS X 10.4.1 > 1. specifying --disable-cp-tools and --disable-gjdoc doesn't seem > to disable them. They were still in the makefile. Removing them by > hand allowed the build to proceed. > > 2. there's a "CLASSPATH" issue with gjdoc which causes it to not > build (which is why I tried to disable it) > > Mac OS X did not have the LD_LIBRARY_PATH issue - it "just worked" > > THis all looks very nice - super job !! > > Regards.....Peter Update for Mac OS X issues - I tried to reproduce the "CLASSPATH" problem but it doesn't happen now. The message then was ... You have no CLASSPATH, I hope it is good checking for java-live... java-live checking for uudecode... yes checking if uudecode can decode base 64 file... yes checking if java-live works... configure: error: The Java VM java- live failed (see config.log, check the CLASSPATH?) make: *** [configure-extra] Error 1 Now it says that there is no antlr.jar (which is correct). And specifying --disable-gjdoc then allowed the configure and build to work OK. So the Mac OS X version appears fine. Thanks.....Peter