Add Libffi-dev installation to the bootstrapping script #180
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
can run: `./railties/exe/rails new cool_app --dev` Inside the Vagrant container.
peterb
changed the title
peterb
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently when you run
./railties/exe/rails new cool_app --devinside the Vagrant container, you get a message: along the lines ofError installing ffi: Failed to build gem native extensionIf
libffi-devis installed, the libffi gem native extensions can compile, which are required when generating a Rails application inside the Vagrant container. See my post on the rails-core mailing list for some background on the motivation, this is one approach. Happy to modify/add to this this based on feedback!