The instructions are probably a bit confusing. It’s saying that you’ve modified your Gemfile on your development machine and just pushed those changes rather than running bundle install BEFORE committing the changes. By running bundle install you will update your Gemfile.lock file. This should be pushed to your server as it’s more important than Gemfile. … Read more
The gem install ffi fails due to the gem trying to build a bundled copy of libffi, which does not work due to assumptions that /usr/bin/env exists and too old libffi copy. However, you can build the ffi gem against the system libffi – install the packages: apt install clang make ruby-dev libffi-dev After that … Read more
For MacOS Catalina, Big Sur, and Monterey: brew install [email protected] bundle config build.libv8 –with-system-v8 bundle config build.therubyracer –with-v8-dir=$(brew –prefix [email protected]) bundle (update version numbers as needed)
I think this is the problem: You have bundler installed to a specific gemset, which is why it’s only available when you’re in your app’s directory (I’m assuming there’s a .rvmrc file in there). You have a few options: Install bundler to a global gemset. rvm gemset use global && gem install bundler If you … Read more
The proper way to do this is outlined here. Since the gemspec is evaluated at package time, you need to do it in a native extension. Don’t worry, it’s not that scary since its still just Ruby code (not compiling C or anything). We are currently using this approach for some client tools for OpenShift … Read more
The Gemfile is wherever you want it to be – usually in the main directory of your project and the name of the file is Gemfile. It’s convenient to have one because it allows you to use Bundler to manage which gems and which versions of each your project needs to run. If you are … Read more
I had the same problem installing under OSX 10.7.3. When installing the gem, my error message was: Building native extensions. This could take a while… ERROR: Error installing bcrypt-ruby: ERROR: Failed to build gem native extension. creating Makefile make compiling bcrypt_ext.c make: /usr/bin/gcc-4.2: No such file or directory make: *** [bcrypt_ext.o] Error 1 Looks like … Read more
This SO Question might help you out. The suggestion there is to add require ‘rake/dsl_definition’ above require ‘rake’ in your Rakefile.
Have you tried specifying rvm –default use after the gemset is created so passing: rvm –default use [email protected] and then seeing if that sticks? Using create and default at the same time isn’t something I’ve tried before, it’s the only thing that strikes me as out of place. Given the discussion below I’d offer this … Read more
You can’t do this exactly, because requiring one file may require others, and Ruby can’t tell the difference between the file that you required and the file that someone else required. You can check out $LOADED_FEATURES for a list of every single thing that’s been required. But you should use Bundler if you want to … Read more