Hi Schalk, I've noticed that myself. It seems that at some point the what gemspec file got corrupted or abandoned or your guess goes here in gold. You've got maybe three options available.
1) Find a pre-built gem in whatever passes for package format on your os. 2) Build your own gemspec to acompany the available source, build and install your own local gem. 3) Find someone who can provide you with some more options. I might be able to help you with option 2 if that's the way you want to go. You'll need a c compiler and MySql installed. I figured out how to do it (so it can't be that hard) when I noticed that mysql-2.7.3 is advertised but doesn't install on my machine and that mysql-2.8 has been available since aug2008. 4) Actually, now that I think of it, maybe we could get someone to add gemspec's to the source, or provide a simple way to do a gem install without a gemspec. That sounds like option 3, above. Rick On Nov 23, 2:35 pm, Schalk Neethling <[EMAIL PROTECTED]> wrote: > Hey all, > > The problems keep coming. Having upgraded everything and upgraded to > Rails 2.2.2 I now wanted to install the MySQL gem as I am getting the > following error when trying to load up the app. > > no such file to load -- mysql > > Normally running gem install mysql works with no problems but, now I get > the following: > > gem install mysql -- --with-mysql-config=C:\InstantRails\mysql\bin > Successfully installed mysql-2.7.3-x86-mswin32 > 1 gem installed > Installing ri documentation for mysql-2.7.3-x86-mswin32... > Installing RDoc documentation for mysql-2.7.3-x86-mswin32... > ERROR: While generating documentation for mysql-2.7.3-x86-mswin32 > ... MESSAGE: Unhandled special: Special: type=17, text="<!-- $Id: > README.html,v 1.20 2006-12-20 05:31:52 tommy Exp $ -->" > ... RDOC args: --op > C:/InstantRails/ruby/lib/ruby/gems/1.8/doc/mysql-2.7.3-x86-mswin32/rdoc > --exclude ext --main README --quiet ext README docs/README.html > (continuing with the rest of the installation) > > The last line is misleading because when I go to the mysql folder after > the installation has completed, it is completely empty. Does anyone have > any idea if there are problems with the MySQL 2.7.3 gem? What else could > be going wrong here? > > Thanks, > Schalk --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
