Re: [Jikesrvm-researchers] Jikes RVM 2.3.2 with SUN JDK 1.4.2

[David P G. <gr...@us...>]

Some versions of Jikes can be used to build Jikes RVM, others are buggy. 
Version 1.20 is known to fail with this assertion failure.  Your best bet 
is either 1.18 or 1.19.  I have never had problems with them building 
Jikes RVM (although some have reported problems with 1.19 on OSX).

I've just updated our userguide to warn people away from Jikes 1.20.

--dave





yau meileng <mei...@ya...>
Sent by: jik...@ww...
04/27/2004 08:05 AM
Please respond to jikesrvm-researchers
 
        To:     jik...@ww...
        cc: 
        Subject:        Re: [Jikesrvm-researchers] Jikes RVM 2.3.2 with 
SUN JDK 1.4.2


hi Michael,
 
yes... the problem is actually because of my jikes not found. I manage to 
set the path for jikes already but yet still encounter this error when I 
./jbuild at rvmBuild:
 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
jbuild.compile: (compiling classes... jikes: symbol.h:1110: bool 
TypeSymbol::IsInner() const: Assertion `(! IsLocal() && ! Anonymous()) || 
(IsNested() && ! ACC_STATIC())' failed.
Aborted
compilation FAILED) jbuild.compile: The Jikes compiler exited with status 
134 while we were building the source file(s): Dummy.java
jbuild.compile: We invoked the Jikes compiler in the directory 
/home/rvmBuild/RVM.classes
jbuild.compile: With the command-line: /usr/bin/jikes -nowarn -g +U 
-classpath .:rvmrt.jar Dummy.java
jbuild.compile: Exiting unexpectedly with status 134.
jbuild.compile: Cleaning up...
jbuild.compile: ...no cleanup was needed.
jbuild.compile:1: some command we just ran (probably with a
     final argument of "unexpected_exit") exited with status 134,
jbuild.compile: The command was killed by signal # 6
jbuild.compile: Aborting execution.
9 s
jbuild: Trouble while running "./jbuild.compile " (exit status
     134); aborting execution
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
What is wrong with this anyway!
 
-meileng-
Michael Haupt <ha...@in...> wrote:
Hi,

yau meileng wrote:
> (c) RVM_FOR_SINGLE_VIRTUAL_PROCESSOR = 0 (SMP support)

just a sidenote: you might run into trouble with this setting. If you 
manage to build the Jikes RVM and it just hangs at startup, set this to 
1 again. For more details, see, for example, 
http://www-124.ibm.com/pipermail/jikesrvm-core/2004-January/000611.html

> At step 10 the build fail with the follwing errors:
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> [...]
> /usr/bin/jikes +F -bootclasspath '' -extdirs '' -sourcepath '' 
> -classpath 
> ../../classpath:../../classpath/external/jaxp/source:../vm/current:.: -d 

> . @classes
> make[1]: /usr/bin/jikes: Command not found
> make[1]: *** [compile-classes] Error 127

This most certainly means that you either have not installed the Jikes 
Java compiler, or the path to the Jikes compiler binary is not set 
properly in your configuration. There is a variable called JIKES that 
should point to the binary. If the compiler is somewhere in the PATH, a 
line like

export JIKES=`which jikes`

does the trick. ;-)

Best regards,

Michael Haupt

-- 
Dipl.-Ing. Michael Haupt ha...@in...
Software Technology Group Phone: ++49 (0) 6151-16-5306
Darmstadt University of Technology Fax: ++49 (0) 6151-16-5410
Hochschulstr. 10, 64283 Darmstadt, Germany
http://www.st.informatik.tu-darmstadt.de/


_______________________________________________
Jikesrvm-researchers mailing list
Jik...@os...
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jikesrvm-researchers
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs