I've tried a million different tutorials and I just can't figure this out. I have all things needed to create the development environment and I just can't get the server to function correctly I suppose. Here's the error I am getting: "The bundled mysql.rb driver has been removed from Rails 2.2. Please install the mysql gem and try again: gem install mysql. /!\ FAILSAFE /!\ Sun Apr 05 00:17:39 -0700 2009 Status: 500 Internal Server E rror dlsym(0x1c44680, Init_mysql): symbol not found - /usr/local/lib/ruby/ gems/1.8/gems/mysql-2.7/lib/mysql.bundle" And then when I got to localhost:3000 and click on the "About your application's environment", I get a red box that says "We're sorry, but something went wrong.We've been notified about this issue and we'll take a look at it shortly" that drops down. I can't find a solution anywhere. Does anyone have any suggestions? Please help! I've spent hours and I can't find anything. Thank You!
on 2009-04-05 12:58
on 2009-04-05 13:01
On Apr 5, 8:19 am, Scott Corgan <ScottCor...@gmail.com> wrote: > I can't find a solution anywhere. > > Does anyone have any suggestions? Please help! I've spent hours and I > can't find anything. > Really hard to be helpful if we don't know what you've tried :-) (Other than to say that your mysql gem is screwed) Fred
on 2009-04-05 16:24
I mean I've tried re installing. I've tried installing with MacPorts. I just keep getting the same error no matter what. Do you know of any sites that can just walk me through step by step on how to get this working in Leopard besides the Hivelogic article. That doesn't work for me. I'm kinda new at Rails so I dunno how I can be more specific. On Apr 5, 4:00 am, Frederick Cheung <frederick.che...@gmail.com>
on 2009-04-05 16:34
On Apr 5, 3:23 pm, Scott Corgan <ScottCor...@gmail.com> wrote: > I mean I've tried re installing. I've tried installing with MacPorts. > I just keep getting the same error no matter what. Do you know of any > sites that can just walk me through step by step on how to get this > working in Leopard besides the Hivelogic article. That doesn't work > for me. I'm kinda new at Rails so I dunno how I can be more specific. > Well to me, specific means (for example) exactly how you installed the mysql gem, how you installed mysql etc. Fred
on 2009-04-05 19:17
Assuming your only issue is MySQL Support on OS X Leopard, did you happen to note this blog? http://blog.flinter.com/2009/01/16/installing-rail... I assume when you first got your Leopard install it was pre-Rails 2.0? I followed these instructions and simply installed MySQL for OS X from the MYSQL install directions and had no issues: http://developer.apple.com/tools/developonrailsleopard.html When I moved from 2.0 to 2.1.1 I followed a similar set of steps - I googled first for any hazards - the one I found was fixed by me installing another gem based on error logs. Though I did not upgrade MySQL yet and I don't use it in my dev environment much - yet. The one problem I saw with 2.2 was having to upgrade Ruby to 1.9 - I think that is required. If you are handy with XCode you can always roll your own - Hive Logic probably has build it yourself directions for everything you'd need: http://hivelogic.com/articles/view/ruby-rails-leopard Hope this helps. - John
on 2009-04-05 20:51
On Apr 5, 6:16 pm, Jferg <johngfergu...@gmail.com> wrote: > > When I moved from 2.0 to 2.1.1 I followed a similar set of steps - I > googled first for any hazards - the one I found was fixed by me > installing another gem based on error logs. Though I did not upgrade > MySQL yet and I don't use it in my dev environment much - yet. > > The one problem I saw with 2.2 was having to upgrade Ruby to 1.9 - I > think that is required. > Rails 2.2 doesn't support ruby 1.9 (rails 2.3.2 is the first version with ruby 1.9 support, but that ruby 1.9 is by no means compulsory) Fred
on 2009-04-06 08:21
I have all the latest gems, rails, and ruby installed. I keep getting the same error, even when the re route of the mysql library. I don't know what else to do. Maybe an uninstall, clean install, and fix might work? On Apr 5, 11:51 am, Frederick Cheung <frederick.che...@gmail.com>
on 2009-04-06 08:59
When I installed here, making rails work with mysql was painful too.. I tryed to install and re-install both the gem and mysql for about 9000 times, using several different giant terminal commands Could only make it work after installing a 32-bit version of mysql and downloading the gem using macports, which gave an error in the installation, but actually worked when I tested.
on 2009-04-06 10:48
I had this issue, and to start with, I followed various blogs to set the location of the mysql libraries etc.. However, when I did it yesterday, I simply installed the 32 BIT mysql package directly from the mysql web site (64 bit wont work apparently). Then I did 'sudo gem install mysql' - and to my amazement, everything worked. I do wish the rails guys had made this a little less painful though - I bet it puts off some newbies from even venturing into rails. Hope this helps Gary
on 2009-04-06 17:02
Gary Taylor wrote: > I had this issue, and to start with, I followed various blogs to set > the location of the mysql libraries etc.. However, when I did it > yesterday, I simply installed the 32 BIT mysql package directly from > the mysql web site (64 bit wont work apparently). Then I did 'sudo > gem install mysql' - and to my amazement, everything worked. Yes, you must use the 32 bit MySQL as far as I know. The Ruby, at least the one installed on Mac OS X 10.5 is 32 bit and need MySQL to be the same. > I do wish the rails guys had made this a little less painful though - > I bet it puts off some newbies from even venturing into rails. Yes this is a bit of a pain, but if you follow all the correct instructions, and don't follow the blogs blindly, then it's really not that bad getting MySQL working with Leopard. Basically (1) make sure you compile the gem for the correct platform (Universal binary builds don't work, which is what gcc uses by default on Leopard) (2) Fix the dylib issue (this is where a lot of the blogs are wrong (make sure the all the paths they show match your actual system). (3) Make sure you've installed the 32 bit MySQL regardless of your system architecture. As far as Rails itself. I use what was pre-installed. I just updated it to the latest version of RubyGems and Rails and I use it all with great success. No macports, which I personally hate, I won't get into why. I did not install my own Ruby, the pre-installed version works fine for me.
on 2009-04-06 17:26
I have found this site to be consistently useful http://newwiki.rubyonrails.org/database-support/mysql I used this command: $ sudo env ARCHFLAGS="-arch i386" gem install mysql -- \ --with-mysql-dir=/usr/local/mysql --with-mysql-lib=/usr/local/mysql/ lib \ --with-mysql-include=/usr/local/mysql/include This was on several different installs of Leopard. Both new Leopard installs, and version of Leopard that had been upgraded from functioning older versions of rails. I had one issue, where the installed version of mysql was too old, but that was fixed after I upgraded to the current version. I am using an older mysql install. I prefer 5.0 over 5.1 right now. 5.0.77 is the current version I am installing. http://dev.mysql.com/downloads/mysql/5.0.html#macosx-dmg Eric
on 2009-04-06 19:03
Did you run this on your Mac: "gem update —system" If so, you might have bricked your install from the get-go. What I did was I re-installed the OS (not a big deal for me at the time) and just ran "gem update" No problems from then on out.
on 2009-04-06 19:34
What are the "latest" gems/rails and ruby that you have installed? here is some information that would be useful to use: $ port list | grep mysql $ mysql5 --version $ port list | grep lang/ruby $ gem list $ ruby -v