[ 
https://issues.apache.org/jira/browse/BUILDR-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152267#comment-13152267
 ] 

Rhett Sutphin commented on BUILDR-614:
--------------------------------------

I just noticed this issue because Antoine mentioned it on the mailing list.  
The provided solution may work when installing the gem from source, but it 
won't work on a packaged gem. That's because the packaged gem's gemspec is the 
result of intepreting buildr.gemspec and then reserializing it.

I think the only possible permanent solution for this (i.e., other than 
manually installing rjb with --platform ruby before installing buildr) would be 
to change buildr to depend on a version of RJB that doesn't ship a separate 
darwin binary. It looks like 1.3.7, 1.3.6, and 1.3.5 would be candidates.
                
> Buildr development - Using rvm, bundler and OSX installs the wrong rjb
> ----------------------------------------------------------------------
>
>                 Key: BUILDR-614
>                 URL: https://issues.apache.org/jira/browse/BUILDR-614
>             Project: Buildr
>          Issue Type: Bug
>         Environment: rvm 1.6.32
> bundler version 1.0.21
> ruby 1.8.7-p352
> OSX 10.6.8
>            Reporter: Russell Teabeault
>            Assignee: Antoine Toulme
>             Fix For: 1.4.7
>
>         Attachments: BUILDR-614.diff, BUILDR-614.diff
>
>
> The Gemfile for buildr specifies rjb as a dependency.  However, when running 
> on OSX and using rvm, the rjb that gets installed is the version compiled 
> against the OSX system ruby instead of the rvm ruby.  This can be fixed by 
> adding the following to the Gemfile:
>   if `uname`.strip == 'Darwin' and ENV["rvm_ruby_string"] != 'system'
>     Gem.platforms = [Gem::Platform::RUBY]
>   end
> I think in the end this is probably an rjb problem but adding this to the 
> Gemfile would be helpful for buildr developers woring with rvm and OSX.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to