History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRUBY-954
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Vladimir Sizikov
Reporter: Albert Strasheim
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JRuby

Shell scripts from JRuby dist tarball built on Windows don't work on Linux due to wrong line endings

Created: 19/May/07 03:18 PM   Updated: 23/Apr/08 10:16 AM
Component/s: Miscellaneous
Affects Version/s: JRuby 1.1
Fix Version/s: JRuby 1.1

Time Tracking:
Not Specified


 Description  « Hide
I checked out the JRuby source on Windows and built jruby-bin-1.0.0RC2.tar.gz on Windows. I then copied over the tarball to a Linux machine, extracted it, and attempted to run JRuby:

[albert@dogbert ~]$ jruby-1.0.0RC2/bin/jruby foo.rb
-bash: jruby-1.0.0RC2/bin/jruby: /bin/bash^M: bad interpreter: No such file or directory

This error is due to the jruby script (and probably the other scripts) having Windows line endings instead of UNIX line endings.

Ant's FixCRLF Task can probably fix this issue.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Charles Oliver Nutter - 30/May/07 04:38 PM
The workaround is to build on Linux. We'll see if we can fix this post 1.0 though.

Charles Oliver Nutter - 23/Oct/07 02:46 PM
Albert: if you're still out there, want to provide a patch for build.xml?

Albert Strasheim - 26/Oct/07 12:03 AM
The easy solution here might be to set a proper svn:eol-style property on the relevant files in the repository.

Charles Oliver Nutter - 27/Oct/07 12:31 PM
I'm not sure that would help, since by the time you've built a dist the files have already been checked out Windows-style.

Thomas E Enebo - 31/Dec/07 12:46 PM
I will point out that windows now has this issue with cygwin since cygwin now requires shell scripts to not have \r\n lines in them. Looks like CRLF ant task can solve this for us.

Vladimir Sizikov - 07/Feb/08 02:08 PM
Fixed in rev. r5861 on trunk.

Charles Oliver Nutter - 23/Apr/08 10:11 AM
Marking bugs with invalid "fixed for release" as fixed in 1.1.