Open
Description
Actually, the scala script for execution contains a non-standard option -Xbootclasspath/a:path. Then, when executing scala script, if you decide to precise a special java virtual machine that does not implement this non-standard option, you will get this error:
** ERROR: unrecognized option '-Xbootclasspath/a:/home/username/scala/lib/jline.jar:/home/username/scala/lib/scala-compiler.jar:/home/username/scala/lib/scala-dbc.jar:/home/username/scala/lib/scala-library.jar:/home/username/scala/lib/scalap.jar:/home/username/scala/lib/scala-swing.jar
For example, in my case, it was with the real time java virtual machine called JamaicaVM which does not support this option.
My solution was to replace -Xbootclasspath/a:path by -Xbootclasspath:path and to add the current directory "." at the bootstrap classpath.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
scabug commentedon Jan 16, 2012
Imported From: https://issues.scala-lang.org/browse/SI-5379?orig=1
Reporter: Antoine Bertout (bertouta)
Affected Versions: 2.9.1
scabug commentedon May 31, 2012
@magarciaEPFL said:
The distribution has to cover the common case, right? The common case is HotSpot. About handling non-common cases, that can best be tackled by those in the community knowledgeable with those scenarios (for example, using JamaicaVM).
Assigning this bug to Community.