Hello all! I just downloaded rubyscript2exe.gem from http://www.erikveen.dds.nl/rubyscript2exe/index.html, but it isn't working. I've done exactly as the manual says, but it outputs the following: Tracing x ... Couldn't execute this command (rc=): <huge block of text with fiule names> I've also given it a go with the .rb file found at http://www.erikveen.dds.nl/rubyscript2exe/download..., but the same thing occurs. If more details are needed, let me know. Thanks in advance for your help!
on 2007-05-27 11:54
on 2007-05-29 13:28
Yannick Grams wrote: > Hello all! > > I just downloaded rubyscript2exe.gem from > http://www.erikveen.dds.nl/rubyscript2exe/index.html, but it isn't > working. I've done exactly as the manual says, but it outputs the > following: > > Tracing x ... > Couldn't execute this command (rc=): > <huge block of text with fiule names> > > I've also given it a go with the .rb file found at > http://www.erikveen.dds.nl/rubyscript2exe/download..., > but the same thing occurs. If more details are needed, let me know. > > Thanks in advance for your help! Forgive the bump, but nobody has replied, and I'm intrigued as to why the program is not working.
on 2007-05-29 15:40
Dear Yannick, welcome to the club of people who don't get any responses to their posts on this list ;-( -- and goodbye, since I'll try to share the little I know with you. I've tried to use rubyscript2exe myself, with mixed success so far (but that's not Erik Venstra's fault), but I always got past this tracing phase within which you got kicked out. Rubyscript2exe executes the ruby script in the tracing phase and it seems that the program can't get through it. Does the underlying ruby script as such work, if you start it from ruby directly ? Do you use any external libraries, gems, other software that you communicate with via pipes etc? Did you put everything you need into a single directory? What OS do you use ? Maybe you try an easy script (print hello-world/ ask for a name and repeat it) first. In my experience, I always got a binary that will work from rubyscript2exe, (on the computer it was created on), but of course had the downsides of all binaries - create it on a 64-bit machine, it won't work on a 32-bit machine, or it asks for some C library which you only have an older version of on another computer. Maybe trying it on some Linux Live distribution might also be an alternative. Over two years, I wrote several emails to Erik at his email address indicated in the help file and got a response that got me further as well... I'd join you to say that I'd also appreciate more responses to questions related to Rubyscript2exe from users of this list, even if they cannot solve all problems at once. Best regards, Axel
on 2007-05-29 15:51
I have recently used rubyscript2exe with out any issues. It might help to either include the script thats causing the problem ,or a link if its large, or minimal example that exhibits the behavior if you don't want to/can't share the real script. Alternatively, giving the full error might help, even with out your script. Cheers Chris
on 2007-05-29 22:57
Thanks for your advice! The answers to yours questions: - Yes, the script works when run directly through Ruby - No, I use no extra libraries or gems, as to try solving the problem, I completely re-installed Ruby, but to no effect - Yes, everything is all in the same directory - I use Microsoft Windows XP Home, SP 2 I may not have mentioned this, but I have used the gem previously, but after I updated my version of Ruby to 1.8.6-25, it has stopped working, regardless of how many re-installs and uninstalls that I do. I have tried it with a simple "Hello World" script, and the same error shows. Here is the exact output from cmd.exe: >Tracing Program.rb >Couldn't execute this command (rc=): >C:\Program Files\Ruby\bin\ruby -r 'rbconfig.rb' -r 'rubygems/rubygems_version.rb' >-r 'thread.so' -r 'thread.rb' -r 'rbconfig/datadir.rb' -r >'rubygems/user_interaction.rb' -r 'socker.so' -r 'timeout.rb' This kind of thing continues and fills the Command Prompt window, and it is all along the same line of "-r 'filename' -r 'filename'" If anybody can give me any suggestions, then I'm all ears!
on 2007-05-30 11:51
> - No, I use no extra libraries or gems, The trace shows that you are including Rubygems. > as to try solving the problem, I completely re-installed > Ruby, but to no effect How did you install Ruby? > I may not have mentioned this, but I have used the gem > previously, but after I updated my version of Ruby to > 1.8.6-25, it has stopped working, regardless of how many > re-installs and uninstalls that I do. Well, that's interesting information. On the other hand, AFAIK, there's no Ruby 1.8.6-25. What am I missing? gegroet, Erik V. - http://www.erikveen.dds.nl/
on 2007-05-30 12:11
> -r 'socker.so' socker.so? Does anybody know where that comes from? gegroet, Erik V. - http://www.erikveen.dds.nl/
on 2007-05-30 14:25
Erik Veenstra schrieb: > Well, that's interesting information. On the other hand, AFAIK, > there's no Ruby 1.8.6-25. What am I missing? OneClickInstaller Ruby-186-25 is actually the Version for Windows. btw - I don't have any problems using RubyScript2Exe for this version. Last week I build a small tool (Command-Line) for some persons and distributed it via RubyScript2Exe. I produced it on WIndows2000, it works fine on WindowsXP and Windows 2000. Wolfgang Nádasi-Donner
on 2007-05-30 17:37
Dear Yannick, I don't have any socker.so installed on my Windows XP installation. My rough intuition tells me that *.so files should be to Linux about what .dll files are to Windows, but even though I could spot a thread.so library on my Windows Xp installation, this socker.so - I suspect - might be causing the problem. I couldn't find it from Google either. Can you test whether you get through with rubyscript2exe when you use a Linux Live distribution ? Best regards, Axel
on 2007-05-30 22:42
By no extra installed gems or libraries, I meant apart from the ones that came pre-installed with the One-Click Installer. Sorry for the confusion! The problem must be something I'm doing or something wrong with my computer, so I'll just have to keep trying. I've downloaded the new RubyScript2Exe but the same thing occurs. Luckily, I can use allinoneruby, so all is not lost. P.S. I'm afraid I won't be able to try it out on a Linux machine.