I'm a Ruby newb, so go easy on me.
I grabbed the Ruby 2.0.0-p247 (x64) and DevKit-mingw64-64-4.7.2 distributions from rubyinstaller.org and everything was fine - passed the
json gem binary install test and all.
When I attempted to install the
pg gem however, I ran into this issue which seems to stump a lot of new ruby users - there are many similar posts on stackoverflow and elsewhere.
bundle check everything appears to be fine, but when I look inside "Gemfile.lock", I see
0.16.0-x86-mingw32 where I expect I should be seeing
The gem is installed and no tools (gem, bundle, etc.) ever complain about this issue - it only surfaces at run-time, when, seemingly, the pg gem simply gets skipped without any notice, warning or error. (which in itself is creepy, but probably has nothing to do with the pg gem as such?)
After half a day of googling and trying to different things, nothing helps, and I finally went and ditched my 64-bit ruby environment, and set up a new 32-bit environment. It doesn't feel right, running a 32-bit environment on a nice fast 64-bit machine, but whatever works, I suppose.
Anyhow, do you think this is a problem with the pg gem, with gem itself, with bundler, or even with the ruby or devkit distribution?
As mentioned, I was able to build and run the json binary gem, so it seems like at least ruby and devkit must be working.
From my limited understanding of gem and bundler, either of those could potentially be at fault, but I'm hoping you can answer that question better than I?
PS: my installed version is 0.16.0, not 0.15.0, but there was no option for that in the Version dropdown on this form.