Re: Building Ruby (was Re: Ruby on Rails 2.0.2/Cygwin Bug)

2008-01-08 Thread Corinna Vinschen
On Jan 2 14:01, Dave Korn wrote: On 02 January 2008 10:25, melvins wrote: Mike Boone wrote: In reference to that /dev/urandom bug I encountered last week, I thought I might try to build Ruby from source on Cygwin and see how it works. I downloaded Ruby 1.8.6-p111 off the

Re: Building Ruby (was Re: Ruby on Rails 2.0.2/Cygwin Bug)

2008-01-02 Thread melvins
Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- View this message in context: http://www.nabble.com/Building-Ruby-%28was-Re%3A-Ruby-on-Rails-2.0.2-Cygwin-Bug%29-tp14505644p14576153.html Sent from the Cygwin list mailing list archive

Re: Building Ruby (was Re: Ruby on Rails 2.0.2/Cygwin Bug)

2008-01-02 Thread Mike Boone
On Jan 2, 2008 5:24 AM, melvins [EMAIL PROTECTED] wrote: I had the same problem with you mike, what I did is I downloaded a stable-snapshot version of ruby, then I copy the missing/strftime.c file to hte 1.8.6 version, run make again, then it now all works. This worked for me too. Both the

RE: Building Ruby (was Re: Ruby on Rails 2.0.2/Cygwin Bug)

2008-01-02 Thread Dave Korn
On 02 January 2008 10:25, melvins wrote: Mike Boone wrote: In reference to that /dev/urandom bug I encountered last week, I thought I might try to build Ruby from source on Cygwin and see how it works. I downloaded Ruby 1.8.6-p111 off the ruby-lang.org website, unpacked it, then

Re: Ruby on Rails 2.0.2/Cygwin Bug

2008-01-02 Thread Mike Boone
On Dec 22, 2007 3:46 PM, Igor Peshansky [EMAIL PROTECTED] wrote: As I mentioned before, I don't use Ruby too often. But I just realized something: to reproduce the error, you needed a require 'nonexistent_file', which will obviously set errno to ENOENT (which is exactly the error you're

Building Ruby (was Re: Ruby on Rails 2.0.2/Cygwin Bug)

2007-12-26 Thread Mike Boone
In reference to that /dev/urandom bug I encountered last week, I thought I might try to build Ruby from source on Cygwin and see how it works. I downloaded Ruby 1.8.6-p111 off the ruby-lang.org website, unpacked it, then ./configure and make. This fails with: ./missing/strftime.c:193: error:

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-22 Thread Corinna Vinschen
On Dec 21 22:13, Mike Boone wrote: I came up with a simple Ruby snippet that reproduces the problem. I'd appreciate it if other Cygwin users would try it. You can change the cause_failure = true line to say false and it will run. --urandom_test.rb-- # Test failure of reading

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-22 Thread Mike Boone
On Dec 22, 2007 7:51 AM, Corinna Vinschen [EMAIL PROTECTED] wrote: Looks like a bug in ruby. First of all, this works fine under Cygwin: Thanks for analyzing this. I'll take it up at comp.lang.ruby and see what happens. http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/284492 Mike

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-22 Thread Mike Boone
Over on the comp.ruby.lang group, I got a reply from Matz, the lead Ruby developer: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/284495 He states: The bug must lie between Cygwin and Ruby. We don't call lseek explicitly. You can clearly see this by doing strace on Linux (or other

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-22 Thread Igor Peshansky
On Fri, 21 Dec 2007, Mike Boone wrote: I came up with a simple Ruby snippet that reproduces the problem. I'd appreciate it if other Cygwin users would try it. You can change the cause_failure = true line to say false and it will run. --urandom_test.rb-- # Test failure of reading

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-21 Thread Mike Boone
I came up with a simple Ruby snippet that reproduces the problem. I'd appreciate it if other Cygwin users would try it. You can change the cause_failure = true line to say false and it will run. --urandom_test.rb-- # Test failure of reading /dev/urandom after failed require # this method is

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-20 Thread Mike Boone
On Dec 19, 2007 11:59 PM, Igor Peshansky [EMAIL PROTECTED] wrote: Well, /dev/urandom certainly exists in Cygwin. I'm not a Ruby expert, but considering that adding a puts() before the file open seems to fix it, I'd look somewhere in the Ruby code. But you can try running the original under

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-20 Thread Frodak Baksik
On Dec 20, 2007 10:28 AM, Mike Boone wrote: On Dec 19, 2007 11:59 PM, Igor Peshansky wrote: Well, /dev/urandom certainly exists in Cygwin. I'm not a Ruby expert, but considering that adding a puts() before the file open seems to fix it, I'd look somewhere in the Ruby code. But you can

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-20 Thread Mike Boone
On Dec 20, 2007 4:29 PM, Frodak Baksik [EMAIL PROTECTED] wrote: On Dec 20, 2007 10:28 AM, Mike Boone wrote: Can you access /dev/urandom outside of ruby? It might be a simpler check to ensure that /dev/urandom is working. I ran all the commands you suggested with no problems. The problem

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-20 Thread Mike Boone
OK, I modified the Rails source code to add the puts statement just above the statement that reads from /dev/urandom. I then ran strace again and looked for the relevant section of the output. I trimmed out the leading numeric stuff so I could run a diff on them. Here is the output of the failing

Ruby on Rails 2.0.2/Cygwin Bug

2007-12-19 Thread Mike Boone
Can anyone running Cygwin and Ruby on Rails comment on this problem? Create a Rails 2.0.2 application and see if it fails with this error: No such file or directory - /dev/urandom I filed a bug on Rails, please read for more details. http://dev.rubyonrails.org/ticket/10544 I'm not sure if this

Re: Ruby on Rails 2.0.2/Cygwin Bug

2007-12-19 Thread Igor Peshansky
On Wed, 19 Dec 2007, Mike Boone wrote: Can anyone running Cygwin and Ruby on Rails comment on this problem? Create a Rails 2.0.2 application and see if it fails with this error: No such file or directory - /dev/urandom I filed a bug on Rails, please read for more details.