I have yet to find a solution for this issue I have tried multiple
things that I have found on google, but yet have i found a solution. If
someone could help me and point me in the right direction I would be
much appreciated.
my gem file already has it, any other solutions? I just decided to do
the package install of mysql to see if i was manually installing it
wrong, and nope same issue still.
On Sun, Apr 11, 2010 at 5:28 PM, Michael Michael [email protected]wrote:
my gem file already has it, any other solutions? I just decided to do
the package install of mysql to see if i was manually installing it
wrong, and nope same issue still.
Michael, did you run the following in the root of your Rails
application:
Yes I did, I kind of gave up for now on this. I can’t seem to figure it
out.
If you could or anyone could help me out would be great.
Thanks again for the response.
Conrad T. wrote:
On Sun, Apr 11, 2010 at 5:28 PM, Michael Michael [email protected]wrote:
my gem file already has it, any other solutions? I just decided to do
the package install of mysql to see if i was manually installing it
wrong, and nope same issue still.
Michael, did you run the following in the root of your Rails
application:
I had similar problem after upgrading to Snow leopard, i had to
reinstall the Mysql gem with right architecture flags.
Michael Michael wrote:
I have yet to find a solution for this issue I have tried multiple
things that I have found on google, but yet have i found a solution. If
someone could help me and point me in the right direction I would be
much appreciated.
I have faced the same problem, and here is how I solved it, with the
list of failures. Note that I have faced the problem only once on this
particular configuration. Elsewhere (PPC and x86_64) the world is
cloudless.
Configuration:
OS: Fedora 12
Arch: PPC64
Rails 3 pre
Gem 1.3.6
Ruby 1.8.8 (I use 1.8.7 on my other machines, but I needed some
extra patches to compile against openssl 1.0—yet another story )
(Fail 1) Installed the gem with Bundler
(Fail 2) Installed the gem with gem, and bundle it with Bundler
(Fail 3) Installed the library manually
Given that my repository assumes we use Bundler, I then did again
(Fail 1). This is the configuration that will work in the following…
At this point, I started to go along the new Rails bootstrap process.
Playing also with IRB (rails c) and Rake, I realized that the gems
are all loaded but mysql. The most interesting:
$ rake db:setup --trace #=> Fail
$ rake -r mysql db:setup --trace #=> Success, although all Mysql
constants are flagged as already initialized…
Which confirms a weird behavior with the load process for the mysql
gem, on that particular architecture.
In the Gemfile, I have then bypassed Gem to load the mysql library
directly:
Database
#gem ‘mysql’
require ‘mysql’
Doing so everything works fine now. I would like to understand what is
happening but I am a bit short in time now Note that this
modification of the Gemfile is not what we want on all machines. Given
that this PPC64 machine is my production server, a simple conditional
to choose between gem or require may be sufficient, waiting for a
proper fix.
I hope this can help you, but I have a rare architecture these days…
Not sure it is applicable directly.