as an aside, I noticed that you put 2.0 in the mono variable, the actually
value of the mono env variable is immaterial, it just needs to be not nil :)
On Tue, Dec 30, 2008 at 12:30 AM, jirapong.na...@gmail.com <
jirapong.na...@gmail.com> wrote:
> Hello Sidu,
>
> quick fix to open Rakefile then c
There are some bugs in mono 2.0 that will prevent you from compiling
IronRuby, your best bet is to use the SVN trunk, though I believe 2.2 works
as well. Also, my github linux branch includes various fixes for linux that
may be necessairy for OSX as well.
On Tue, Dec 30, 2008 at 1:11 AM, jirapong
Hi JD,
yes. but follow error was throw.
Macintosh-2:ironruby Jirapong$ rake compile mono=1 --trace
(in /Users/Jirapong/ironruby)
** Invoke compile (first_time)
** Invoke happy (first_time)
** Execute happy
** Invoke clean_build (first_time)
** Invoke happy
** Execute clean_build
** Invoke
That would be a mistake on my part it looks like. If you switch the "\" in the
Rakefile imports with "/", does it work? If so, I'll make the change and push
it out tonight or tomorrow.
JD
-Original Message-
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyfor
Hello Sidu,
quick fix to open Rakefile then change 'rake\xxx' to 'rake/xxx'.
however, you will get another error.
Macintosh-2:ironruby-r180 Jirapong$ rake compile mono=2.0
(in /Users/Jirapong/ironruby-r180)
---
dlr_core
Hey guys,
I'm running on OS X 10.5.5 with Mono 2.0 (installed via Ports). I ran
rake compile mono=1
I do have pathname2 installed and am using IronRuby trunk revision 180.
I get the following error:
~/Work/ruby/ironruby$ rake compile mono=1 --trace
(in /Users/schonira/Work/ruby/ironruby)
rake
tfpt review "/shelveset:raise;REDMOND\sborde"
Comment :
Implements Thread#raise using Thread.Abort, and added tests for it
Implemented stress mode (RubyOptions.UseThreadAbortForSyncRaise) which found
more issues. Fixed most but not all
Enabled test for timeout as well
Remaining work (
