Hello Matthew,

So, was your mysql gem compiled during the install sequence?
Is the creation date for mysql.so newer than for the other files?

If that's a definite "can't tell" or just to be sure, uninstall the
gem and reinstall with  the --verbose flag.

  gem uninstall mysql --version=2.8
  gem install mysql --verbose

This should give you the full compilation sequence - very useful stuff
if you're interested in knowing how it's compiled.

Rick

On Nov 29, 9:53 am, Matthew Phillips <[EMAIL PROTECTED]
s.net> wrote:
> Rick wrote:
> > Can you determine what dates are associated with the files?  In
> > particular, was mysql.so created when you did the "gem install..."?
>
> > Also, the test.rb can be usefull.  Assuming you have a mysql database
> > named "testDB" that is owned by user "test" who's mysql password is
> > "test", the following command:
>
> > ruby ./test.rb -- localhost test test testDB
>
> > will run an array of tests on your mysql ruby access.  They should ALL
> > pass.
>
> > Rick
>
> > On Nov 26, 10:05 pm, Wes Gamble <[EMAIL PROTECTED]>
>
> Rick, here's what I get when I run the test.rb:
>
> C:\Development\ruby\lib\ruby\gems\1.8\gems\mysql-2.7.3-x86-mswin32\ext>ruby
> test
> .rb -- localhost test test testDB
> Loaded suite test
> Started
> .........C:/Development/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:3
> 1: [BUG] Segmentation fault
> ruby 1.8.6 (2007-09-24) [i386-mswin32]
>
> This application has requested the Runtime to terminate it in an unusual
> way.
> Please contact the application's support team for more information.
> --
> Posted viahttp://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" 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/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to