Issue #8879 has been updated by nagachika (Tomoyuki Chikanaga).

Status changed from Open to Feedback

Hello,

I cannot reproduce this (transfer binary compiled on an environment (darwin 12.4.0/x86_64/clang-425.0.28(based on LLVM 3.2svn)) to another (dawrin 12.4.0/x86_64).

We need more information.
Cf) clang version, OS X version and architecture on both system, configure options. What's happen when compiled with optimization level (-O0) etc...

Regards.
----------------------------------------
Bug #8879: String#to_r fails after moving ruby to other OSX system
https://bugs.ruby-lang.org/issues/8879#change-41828

Author: mpapis (Michal Papis)
Status: Feedback
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


=begin
I got reported by users (((<rvm issue 2189|URL:https://github.com/wayneeseguin/rvm/issues/2189>))) that a static binary compiled for OSX after moving to other system fails for the method (({String#to_r})):
 ruby -e 'puts ".8".to_r'
 0
The same binary checked on the build system produces proper result:
 ruby -e 'puts ".8".to_r'
 4/5
Also the same version compiled from source on the target system produces proper result:
 ruby -e 'puts ".8".to_r'
 4/5
Please help me debug the problem, can it be related to compilation with (({clang}))?
=end



-- 
http://bugs.ruby-lang.org/