[#JRUBY-1426] error occurs when attempting to disable jit at the command line on windows

JRuby

error occurs when attempting to disable jit at the command line on windows

Created: 12/Oct/07 04:35 PM Updated: 22/Dec/07 06:28 AM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

JRuby 1.1b1, JRuby 1.0.2

Time Tracking:

Not Specified

File Attachments:	1. jrubyvmopts_fix.patch (0.7 kb)
Environment:	windows xp, java 1.6, jruby rev 4581

Description

« Hide

Eror occurs when attempting to disable jit at the command line on windows. I suspect it has something to do with the equals sign. Without the property setter, everything works fine.

starting webrick

>jruby -O -J-server -J-Djruby.jit.enabled=false script/server
Error opening script file: false (The system cannot find the file specified)

same deal for irb

>jruby -O -J-server -J-Djruby.jit.enabled=false -S irb
Error opening script file: false (The system cannot find the file specified)

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Charles Oliver Nutter - 19/Oct/07 06:01 PM

This is a problem with the jruby batch file on windows, and unfortunately none of us are really batch file experts. We could use some help on this and a couple other jruby batch file bugs.

[ Permlink | « Hide ]

Alex Durgin - 20/Oct/07 02:19 AM

The situation is that equal sign and semicolon cannot be passed as arguments to a batch file. The batch system replaces these characters with whitespace. The batch system views -J-Djruby.jit.enabled=false as two seperate arguments would effectively be referenced as %1 and %2. Perhaps the reasonable solution is to use the attached patch, which allows for these properties to be set when quoted (i.e. "-J-Djruby.jit.enabled=false"). Properties such as -J-server do not need to be quoted.

Here is the Microsoft kb explaining the issue:

http://support.microsoft.com/kb/71247

[ Permlink | « Hide ]

Charles Oliver Nutter - 25/Oct/07 04:36 PM

Assigning windows-related bug (with a patch, no less) to Nick.