You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Foward: I solved this. Just want to document it for you.
I switched from RVM to RBENV. I tried to run "bundle" on a project and got this:
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
/Users/ryanbosinger/.rbenv/versions/2.0.0-p353/bin/ruby extconf.rb
/Users/ryanbosinger/.rbenv/versions/2.0.0-p353/bin/ruby: invalid option -P (-h will show valid options) (RuntimeError)
It turns out the problem was that my app folder was in a directory called "Local Projects". The space threw it off and I think that's where the -P option was coming from (the start of "Projects").
This is on MacOS 10.9. I'm not sure if it's an rbenv problem, a bundler problem or just a system thing. The directory name wasn't an issue with my RVM set-up though.
The text was updated successfully, but these errors were encountered:
Might be an rbenv bug with failing to escape paths with spaces somewhere.
When you ran bundle install, did you install into the project's directory (with --standalone or --path=vendor/bundle), or you did a default bundle install which installs into system gems (for that Ruby version)?
Foward: I solved this. Just want to document it for you.
I switched from RVM to RBENV. I tried to run "bundle" on a project and got this:
It turns out the problem was that my app folder was in a directory called "Local Projects". The space threw it off and I think that's where the -P option was coming from (the start of "Projects").
This is on MacOS 10.9. I'm not sure if it's an rbenv problem, a bundler problem or just a system thing. The directory name wasn't an issue with my RVM set-up though.
The text was updated successfully, but these errors were encountered: