Is this a bug?

Ruby JRuby
1

$ gem install faster_rubygems

jruby 1.4.0RC2 (ruby 1.8.7 patchlevel 174) (2009-10-21 7e77f32) (Java
HotSpot™ Client VM 1.6.0_13) [x86-java]
JRuby limited openssl loaded. gem install jruby-openssl for full
support.
http://jruby.kenai.com/pages/JRuby_Builtin_OpenSSL
Building native extensions. This could take a while…
rake aborted!
Don’t know how to build task ‘2>&1’
Thanks!
-r

2

Hi Roger,

Yes, this is a bug, and of my least favorite kind: it involves
Windows, JRuby’s ShellLauncher and shell redirection, all in one
bundle. :slight_smile:

Please file it in JIRA.

Thanks,
–Vladimir

On Sun, Nov 1, 2009 at 12:13 AM, Roger P. [email protected]
wrote:

Thanks!

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
3

As a workaround, type the following before starting the installation
process:

set rake=jruby -S rake

That would allow to install the gem.

Sweet that worked.

Btw, this faster_rubygems approach is interesting, and it reduces the
gem loading in JRuby case quite significantly.

Nice. It’s basically gem_prelude for 1.8 – perhaps with jruby’s magic
they could let us get the benefits of gem_prelude for both :slight_smile:
-r

4

Roger,

As a workaround, type the following before starting the installation
process:

set rake=jruby -S rake

That would allow to install the gem.

Btw, this faster_rubygems approach is interesting, and it reduces the
gem loading in JRuby case quite significantly.

Thanks,
–Vladimir

On Sun, Nov 1, 2009 at 12:04 PM, Vladimir S. [email protected]
wrote:

Don’t know how to build task ‘2>&1’

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
5

Hi Roger, folks,

On Sun, Nov 1, 2009 at 12:46 PM, Vladimir S. [email protected]
wrote:

As a workaround, type the following before starting the installation process:

set rake=jruby -S rake

That would allow to install the gem.

The root problem has been fixed on JRuby’s master branch, so the
workaround is only needed for JRuby 1.4. With the latest development
version everything sshould work as-is with no tweaks.

Thanks,
–Vladimir

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
6

The root problem has been fixed on JRuby’s master branch, so the
workaround is only needed for JRuby 1.4. With the latest development
version everything sshould work as-is with no tweaks.

Thanks for your work on this.