On Aug 8, 2008, at 19:18 , ippalix@gmail.com wrote:

> This doesn't work on my XP machine with newest oneclick rubyinstall
> and rubygems 1.2 (same Gem::Exception error as usual)
> I've tried with both rubyscript2exe and rubyscript2exe.rb. Do you have
> any other workaround ideas until something is made about rubygems?

While there IS a fix that we can add to a file in rubygems, I think it
is necessary to point out that rubyscript2exe is going to have these
problems again and again. Depending on $LOADED_FEATURES is going to be
problematic.

Also, are you sure you added "require 'rubygems'" at the top of your
app? It really should fix the issue.

On 9 Aug, 11:52, Ryan Davis <ryand-r...@zenspider.com> wrote:
> On Aug 8, 2008, at 19:18 , ippa...@gmail.com wrote:
>
> > This doesn't work on *my XP machine with newest oneclick rubyinstall
> > and rubygems 1.2 (same Gem::Exception error as usual)
> > I've tried with both rubyscript2exe and rubyscript2exe.rb. Do you have
> > any other workaround ideas until something is made about rubygems?
>
> While there IS a fix that we can add to a file in rubygems, I think it *
> is necessary to point out that rubyscript2exe is going to have these *
> problems again and again. Depending on $LOADED_FEATURES is going to be *
> problematic.
>
> Also, are you sure you added "require 'rubygems'" at the top of your *
> app? It really should fix the issue.


I've tried with and without require 'rubygems' on top of hello.rb,
actually I've tried all possible combinations of theese 4 lines:
---
require "rubygems"
# require "rubyscript2exe"
# exit if RUBYSCRIPT2EXE.is_compiling?
puts "hello world!"
---

"rubyscript2exe hello.rb" always gives me this: http://pastie.org/250556

(The remote_fetcher.rb:19: uninitialized constant Gem::Exception
(NameError) error)

Hi.

I'm experiencing the same error in rubyscript2exe and I tried this fix as well. I removed RUBY_OPT from my environment variables and tried to run rubyscript2exe on this script:

require 'rubygems'
puts "asdf"

Could somebody elaborate on the fix that will solve this in the rubygems file?

Well, it's working now, for me. On my machine the gem version of the script doesn't work with the fix, but the .rb version (http://www.erikveen.dds.nl/rubyscrip...yscript2exe.rb) does.

unknown wrote:
> On 9 Aug, 11:52, Ryan Davis <ryand-r...@zenspider.com> wrote:
>> problematic.
>>
>> Also, are you sure you added "require 'rubygems'" at the top of your �
>> app? It really should fix the issue.
>
>
> I've tried with and without require 'rubygems' on top of hello.rb,
> actually I've tried all possible combinations of theese 4 lines:
> ---
> require "rubygems"
> # require "rubyscript2exe"
> # exit if RUBYSCRIPT2EXE.is_compiling?
> puts "hello world!"
> ---
>
> "rubyscript2exe hello.rb" always gives me this: http://pastie.org/250556
>
> (The remote_fetcher.rb:19: uninitialized constant Gem::Exception
> (NameError) error)

Hi guys,

I am a newbie with ruby. I have an identical problem as described above
and my output matches http://pastie.org/250556. Is there a workaround /
fix ? Have I missed anything?

I am just using helloworld.rb

Much appreciated..
Andy.
--
Posted via http://www.ruby-forum.com/.