On Dec 6, 12:33 am, Michael Klishin <[EMAIL PROTECTED]> wrote: > On 06.12.2008, at 0:13, dmitry.ilyashevich wrote: > > > Yes, I see that but I can't get why... > > I took a look at RubyInline source and it uses rbconfig under the > covers. I then tried to trace > > RbConfig::CONFIG['arch'] > > on two Rubies I have installed (1.8.6 and 1.9.1 HEAD). What is > interesting, they yield different architecture information: > > 1.8.6: > i686-darwin9.4.0 > > 1.9.1: > i386-darwin9.5.0 > > So my first idea is, maybe you multiple ruby installations interfere. > It's env-specific and I cannot really help much with tracking it down. > Another idea is to try setting CARCH and CHOST and run Merb again. > Compiler *may* hook it up. > I cannot give any other advice at this moment, need to investigate all > the gory details of Ruby config first.
$ irb irb(main):001:0> require 'rbconfig' => true irb(main):002:0> RbConfig::CONFIG['arch'] => "i486-linux" I have only ruby1.8 installed and no ruby 1.9 $ ls /usr/bin/ruby* /usr/bin/ruby /usr/bin/ruby1.8 $ ruby -v ruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux] I set CARCH to i486-linux and CHOST to i486-pc-linux-gnu-4.3.2 and get the same error. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
