2016-06-20 1 views
2

En utilisant rbenv et Rails 4.2.6, quand je lance bundle exec rails s ou bundle exec rails c, je vois ce qui suit:rails serveur et la console ne se charge pas

Ignoring sqlite3-1.3.11 because its extensions are not built. Try: gem pristine sqlite3 --version 1.3.11 

C'est tout, rien ne se passe. Si je puis stop spring et run bundle exec rails c, apparaît ce qui suit:

Ignoring sqlite3-1.3.11 because its extensions are not built. Try: gem pristine sqlite3 --version 1.3.11 
Ignoring sqlite3-1.3.11 because its extensions are not built. Try: gem pristine sqlite3 --version 1.3.11 
Ignoring sqlite3-1.3.11 because its extensions are not built. Try: gem pristine sqlite3 --version 1.3.11 
dyld: lazy symbol binding failed: Symbol not found: _rb_data_typed_object_alloc 
    Referenced from: /Users/nandersen/Projects/the-lunch/vendor/bundle/gems/debug_inspector-0.0.2/lib/debug_inspector.bundle 
    Expected in: flat namespace 

dyld: Symbol not found: _rb_data_typed_object_alloc 
    Referenced from: /Users/nandersen/Projects/the-lunch/vendor/bundle/gems/debug_inspector-0.0.2/lib/debug_inspector.bundle 
    Expected in: flat namespace 

Toute idée de ce qui ne va pas ici? Merci!

Mise à jour: ajouter du contenu de Gemfile et ouput du paquet installer

Gemfile:

source 'https://rubygems.org' 

ruby "2.3.1" 
gem 'rails', '4.2.6' 
gem 'pg' 
gem 'sass-rails', '~> 5.0' 
gem 'uglifier', '>= 1.3.0' 
gem 'coffee-rails', '~> 4.1.0' 
gem 'jquery-rails' 
gem 'turbolinks' 
gem 'jbuilder', '~> 2.0' 
gem 'sdoc', '~> 0.4.0', group: :doc 
gem 'simple_form' 
gem "puma" 
gem 'dotenv-rails', :groups => [:development, :test] 
gem 'quiet_assets', :group => :development 
gem "rails_12factor" 
gem 'slack-ruby-client' 
gem 'rails-i18n', github: 'svenfuchs/rails-i18n', branch: 'rails-4-x' 
gem 'bootstrap-sass', '~> 3.3.6' 

group :development, :test do 
    gem 'byebug' 
    gem 'rspec-rails', '~> 3.4' 
    gem 'factory_girl_rails', '~> 4.0' 
end 

group :development do 
    gem 'web-console', '~> 2.0' 
    gem 'guard' 
    gem 'guard-rspec', require: false 
    gem 'terminal-notifier-guard' 
    gem 'spring' 
end 

Sortie de bundle install:

Using rake 11.2.2 
Using i18n 0.7.0 
Using json 1.8.3 
Using minitest 5.9.0 
Using thread_safe 0.3.5 
Using builder 3.2.2 
Using erubis 2.7.0 
Using mini_portile2 2.1.0 
Using pkg-config 1.1.7 
Using rack 1.6.4 
Using mime-types-data 3.2016.0521 
Using arel 6.0.3 
Using execjs 2.7.0 
Using debug_inspector 0.0.2 
Using sass 3.4.22 
Using byebug 9.0.5 
Using coderay 1.1.1 
Using coffee-script-source 1.10.0 
Using thor 0.19.1 
Using concurrent-ruby 1.0.2 
Using diff-lcs 1.2.5 
Using dotenv 2.1.1 
Using multipart-post 2.0.0 
Using ffi 1.9.10 
Using formatador 0.2.5 
Using gli 2.14.0 
Using rb-fsevent 0.9.7 
Using ruby_dep 1.3.1 
Using lumberjack 1.0.10 
Using nenv 0.3.0 
Using shellany 0.0.1 
Using method_source 0.8.2 
Using slop 3.6.0 
Using guard-compat 1.2.1 
Using rspec-support 3.4.1 
Using hashie 3.4.4 
Using multi_json 1.12.1 
Using pg 0.18.4 
Using puma 3.4.0 
Using bundler 1.12.5 
Using rails_serve_static_assets 0.0.5 
Using rails_stdout_logging 0.0.5 
Using tilt 2.0.5 
Using websocket-extensions 0.1.2 
Using spring 1.7.1 
Using terminal-notifier-guard 1.7.0 
Using rdoc 4.2.2 
Using tzinfo 1.2.2 
Using nokogiri 1.6.8 
Using rack-test 0.6.3 
Using mime-types 3.1 
Using autoprefixer-rails 6.3.6.2 
Using uglifier 3.0.0 
Using binding_of_caller 0.7.2 
Using coffee-script 2.4.1 
Using sprockets 3.6.1 
Using faraday 0.9.2 
Using rb-inotify 0.9.7 
Using notiffany 0.1.0 
Using pry 0.10.3 
Using rspec-core 3.4.4 
Using rspec-expectations 3.4.0 
Using rspec-mocks 3.4.1 
Using rails_12factor 0.0.3 
Using websocket-driver 0.6.4 
Using sdoc 0.4.1 
Using activesupport 4.2.6 
Using loofah 2.0.3 
Using mail 2.6.4 
Using bootstrap-sass 3.3.6 
Using faraday_middleware 0.10.0 
Using listen 3.1.5 
Using rspec 3.4.0 
Using rails-deprecated_sanitizer 1.0.3 
Using globalid 0.3.6 
Using activemodel 4.2.6 
Using factory_girl 4.7.0 
Using jbuilder 2.5.0 
Using rails-html-sanitizer 1.0.3 
Using slack-ruby-client 0.7.4 
Using guard 2.14.0 
Using rails-dom-testing 1.0.7 
Using activejob 4.2.6 
Using activerecord 4.2.6 
Using guard-rspec 4.7.2 
Using actionview 4.2.6 
Using actionpack 4.2.6 
Using actionmailer 4.2.6 
Using railties 4.2.6 
Using sprockets-rails 3.0.4 
Using simple_form 3.2.1 
Using coffee-rails 4.1.1 
Using dotenv-rails 2.1.1 
Using factory_girl_rails 4.7.0 
Using jquery-rails 4.1.1 
Using quiet_assets 1.1.0 
Using rails-i18n 4.0.8 from git://github.com/svenfuchs/rails-i18n.git (at [email protected]) 
Using rspec-rails 3.4.2 
Using rails 4.2.6 
Using sass-rails 5.0.4 
Using web-console 2.3.0 
Using turbolinks 2.5.3 
Bundle complete! 25 Gemfile dependencies, 102 gems now installed. 
Bundled gems are installed into ./vendor/bundle. 

Mise à jour 2 - ajouté bundle exec gem pristine --all

bundle exec gem pristine --all 
Restoring gems to pristine condition... 
Restored rake-11.2.2 
Restored i18n-0.7.0 
Skipped json-1.8.3, it is a default gem 
Restored minitest-5.9.0 
Restored thread_safe-0.3.5 
Restored tzinfo-1.2.2 
Restored activesupport-4.2.6 
Restored builder-3.2.2 
Restored erubis-2.7.0 
Restored mini_portile2-2.1.0 
Restored pkg-config-1.1.7 
Building native extensions. This could take a while... 
ERROR: While executing gem ... (Gem::Ext::BuildError) 
    ERROR: Failed to build gem native extension. 

    current directory: /Users/nandersen/Projects/the-lunch/vendor/bundle/gems/nokogiri-1.6.8/ext/nokogiri 
/Users/nandersen/.rbenv/versions/2.3.1/bin/ruby -r ./siteconf20160620-6035-1m3373p.rb extconf.rb 
Ignoring sqlite3-1.3.11 because its extensions are not built. Try: gem pristine sqlite3 --version 1.3.11 
/Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/spec_set.rb:95:in `block in materialize': Could not find nokogiri-1.6.8 in any of the sources (Bundler::GemNotFound) 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/spec_set.rb:88:in `map!' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/spec_set.rb:88:in `materialize' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/definition.rb:140:in `specs' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/definition.rb:185:in `specs_for' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/definition.rb:174:in `requested_specs' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/environment.rb:19:in `requested_specs' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:14:in `setup' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler.rb:95:in `setup' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/setup.rb:19:in `<top (required)>' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' 
    from /Users/nandersen/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' 

extconf failed, exit code 1 

Gem files will remain installed in /Users/nandersen/Projects/the-lunch/vendor/bundle/gems/nokogiri-1.6.8 for inspection. 
Results logged to /Users/nandersen/Projects/the-lunch/vendor/bundle/extensions/x86_64-darwin-15/2.3.0-static/nokogiri-1.6.8/gem_make.out 
+1

Pourriez-vous nous montrer votre Gemfile, et le résultat de 'bundle install'? –

+1

Oui, j'ai ajouté l'information à la question initiale @LarryLv. – Linus

Répondre

2

Le problème est debug_inspector petit bijou, vous pouvez essayer d'enlever web-console bijou dans votre Gemfile, bundle install et exécutez à nouveau le serveur.

MISE À JOUR:

Ou si vous souhaitez garder le joyau web-console, vous pouvez essayer d'enlever toutes les pierres précieuses que vous avez installé, et re-paquet les installer à nouveau. Selon ce numéro sur rails/web-console.

+0

Je l'ai fait comme vous l'avez suggéré mais maintenant la première erreur réapparaît, elle ne charge pas plus loin que le premier message d'erreur que j'ai posté dans ma question. – Linus

+0

Pourriez-vous essayer ce 'bundle exec gem pristine --all' et exécuter' bundle exec rails c' à nouveau? –

+0

J'ai mis à jour la question avec la sortie de 'bundle exec gem pristine --all'. – Linus