September 2009 - MacRuby-devel - lists.macosforge.org

Fail
by Wayne Seguin 03 Sep '09

03 Sep '09

Hello everyone, Background: I am trying to add MacRuby support to a tool called rvm "Ruby Version Manager" The commands I am using to build and install MacRuby are currently (from rake -T): rake macruby:build framework_instdir=~/.rvm/macruby-head framework_name=/macruby-head --trace rake framework:install framework_instdir=~/.rvm/macruby-head framework_name=/macruby-head --trace This is done every time against a *fresh* clone of: git://github.com/masterkain/macruby.git I am currently running into the following error with the above: http://pastie.org/private/n8wx6kigcojc5rdqllni6w My real requirements are that I can specify the destination directory to install to (example: ~/.rvm/macruby-head). So if I should be using different commands to build & install please let me know. Any help would be greatly appreciated. Thank you for your attention, ~Wayne P.S. Nightly builds would be far superior to having rvm users build themselves.

2 1

Re: [MacRuby-devel] [MacRuby] #12: Support DYLD_FRAMEWORK_PATH for loading
by MacRuby 02 Sep '09

02 Sep '09

#12: Support DYLD_FRAMEWORK_PATH for loading -----------------------------+---------------------------------------------- Reporter: ben@… | Owner: lsansonetti@… Type: enhancement | Status: closed Priority: minor | Milestone: MacRuby 0.5 Component: MacRuby | Resolution: fixed Keywords: | -----------------------------+---------------------------------------------- Changes (by lsansonetti@…): * status: reopened => closed * resolution: => fixed * milestone: => MacRuby 0.5 Comment: Thanks for the patch, applied in r2454. -- Ticket URL: <http://www.macruby.org/trac/ticket/12#comment:6> MacRuby <http://macruby.org/>

1 0

[MacRuby] #170: rake clean target does not delete miniruby
by MacRuby 02 Sep '09

02 Sep '09

#170: rake clean target does not delete miniruby ---------------------------+------------------------------------------------ Reporter: jkh@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: MacRuby 0.4 Component: MacRuby | Keywords: ---------------------------+------------------------------------------------ See subject line. One frequent problem for people following -trunk is that internal changes to MacRuby can cause older versions of the objects or miniruby itself to cause heisenbugs in the build process. This leads to frequent "rake clean" and even "rm -rf /Library/Frameworks/MacRuby.framework" phases, to keep cross-contamination to a minimum, so "rake clean" should do its job better by also cleaning the miniruby binary -- Ticket URL: <http://www.macruby.org/trac/ticket/170> MacRuby <http://macruby.org/>

1 2

Segmentation fault for classes with multiple modules chained with super
by Alexey Borzenkov 01 Sep '09

01 Sep '09

The following program causes segmentation fault for me with the latest macruby trunk: class A def somemethod puts "A::somemethod" end end module B def somemethod super puts "B::somemethod" end end module C def somemethod super puts "C::somemethod" end end class D < A include B include C def somemethod super puts "D::somemethod" end end obj = D.new obj.somemethod Thanks to http://weblog.rubyonrails.org/2009/8/31/three-reasons-love-responder I just found that modules can be chained via super like that, so I immediately went to check it out, and in MRI 1.8 it works fine. I wanted to see it in 1.9, so I checked with macruby and it caused segmentation fault. I recompiled latest macruby trunk and it's still happening. As stated in the README.rdoc I'm using llvm trunk at revision 72741. Is it llvm or macruby bug? Oddly, under gdb it just freezes, can't even see any stack trace. :-/

3 4