Re: [Ironruby-core] [ANN] IronRuby 1.1.1 Released!

2010-10-29 Thread Jirapong Nanta
y installed builder-2.1.2 1 gem installed I'm also post the workaround at - http://ironruby.codeplex.com/workitem/5326 <http://ironruby.codeplex.com/workitem/5326>Hope this help util I can came up with permanent solution. Cheers, -Jirapong On Thu, Oct 28, 2010 at 12:43 AM, Michael Le

Re: [Ironruby-core] [ANN] IronRuby 1.1.1 Released!

2010-10-25 Thread Jirapong Nanta
x27; C:/Program Files (x86)/IronRuby 1.1/Lib/ruby/1.9.1/rubygems/gem_runner.rb:58:in `run' C:/Program Files (x86)/IronRuby 1.1/bin/gem:25 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC> I'm seeing what i can do here. Best, -Jirapong On Mon, Oct 25, 2010 at 10:34 P

Re: [Ironruby-core] Contributions

2010-10-25 Thread Jirapong Nanta
Hello Tomas, I would like to continue my work with OpenSSL. I will re-fork IronRuby and update my progress here. Best, -Jirapong On Sat, Oct 23, 2010 at 11:24 PM, Tomas Matousek < tomas.matou...@microsoft.com> wrote: > Hi Gøran, > > Good to see your interest. > > > &

Re: [Ironruby-core] OpenSSL::X509::Certificate + rubyspecs

2009-08-16 Thread Jirapong Nanta
Hello Jim, I got it update with some modification with MutableString.CreateAscii().. please pull again. Thanks, -Jirapong On Fri, Aug 14, 2009 at 12:36 AM, Jim Deville wrote: > Jirapong, > > Can you update to the latest on Github? > > > > Thanks, > > > > JD

Re: [Ironruby-core] OpenSSL::X509::Certificate + rubyspecs

2009-08-12 Thread Jirapong Nanta
Hello all, all modification as Shri's reviewed able to find at bed5f4c3ae97d5ecb18adc3827901cd5f18389cd<http://github.com/Jirapong/ironruby/commit/bed5f4c3ae97d5ecb18adc3827901cd5f18389cd> *Changes:* 1. Validate all spec with MRI 2. Remove /*!*/ from Value Type 3. C

[Ironruby-core] OpenSSL::X509::Certificate + rubyspecs

2009-07-23 Thread Jirapong Nanta
s for issuer,subject,public_key,serial,and version - tagged the fails rubyspes http://github.com/Jirapong/ironruby/commit/40ddbcb700e402a43ad387cf69005a0795a033fb Thank you, -Jirapong ___ Ironruby-core mailing list Ironruby-core@rubyforge.org

Re: [Ironruby-core] FW: MindTouch Wik.is Upgrade

2008-07-09 Thread Jirapong Nanta
Hello John, website show - reference to undefined name 'syntax' ..for all block. Thanks, -Jirapong On Wed, Jul 9, 2008 at 5:44 AM, John Lam (IRONRUBY) <[EMAIL PROTECTED]> wrote: > FYI > > > > Thanks, > > -John > > > > *From:* MindTouch [ma

Re: [Ironruby-core] Mono build update..

2008-07-08 Thread Jirapong
Hi, do you build on Mac? the UserProfile is where your home directory. you might try, before compile USERPROFILE=[your home dir] export USERPROFILE Hope this help, -Jirapong On Jul 8, 2008, at 12:21 PM, Unnikrishnan Nair <[EMAIL PROTECTED]> wrote: Finally I got mono to

Re: [Ironruby-core] spec changes

2008-07-07 Thread Jirapong Nanta
Hi Unni, Did you check this out? - http://sparcs.kaist.ac.kr/~tinuviel/download/IronRuby/ - http://flanders.co.nz/2008/02/05/compiling-mono-and-ironruby-on-osx-leopard/ Hope this helps, -Jirapong 2008/7/7 Unnikrishnan Nair <[EMAIL PROTECTED]>: > Thanks Jim, I have a test program t

Re: [Ironruby-core] HOME and USERPROFILE aliasing under Windows

2008-07-03 Thread Jirapong
same problem reported at #20475. and i agree that HOME Env should handle by that class -Jirapong On Jul 2, 2008, at 5:31 AM, "John Lam (IRONRUBY)" <[EMAIL PROTECTED]> wrote: MRI currently expects the HOME environment variable to be set under Windows. Various operations

Re: [Ironruby-core] SVN r118 and RubySpec integration

2008-07-01 Thread Jirapong Nanta
nds 1 file, 5 examples, 17 expectations, 0 failures, 0 errors also successful to run: rake regression Thanks, -Jirapong On Wed, Jul 2, 2008 at 12:55 AM, John Lam (IRONRUBY) <[EMAIL PROTECTED]> wrote: > Doh! Thanks for the fix! > > > > Thanks, > > -John > > >

Re: [Ironruby-core] SVN r118 and RubySpec integration

2008-07-01 Thread Jirapong Nanta
Hi John, It was fail to run... attached file is the fixed version. Thank you, -Jirapong On Tue, Jul 1, 2008 at 11:53 PM, John Lam (IRONRUBY) <[EMAIL PROTECTED]> wrote: > Can you try out r119 that I just pushed out? It should have a test that > catches the wrong folder problem