Reputation: 1
I get this error when attempting to use the rails generate
commands:
gem install minitest
WARNING: Nokogiri was built against LibXML version 2.7.3, but has dynamically loaded 2.7.8
Could not open library 'libgtk-x11-2.0': dlopen(libgtk-x11-2.0, 13): image not found.
Could not open library 'libgtk-x11-2.0.dylib': dlopen(libgtk-x11-2.0.dylib, 13): image not found.
Could not open library 'libgtk-x11-2.0.so.0': dlopen(libgtk-x11-2.0.so.0, 13): image not found.
Could not open library 'libgtk-x11-2.0.so.0.dylib': dlopen(libgtk-x11-2.0.so.0.dylib, 13): image not found.
Could not open library 'libgtk-x11-2.0.so': dlopen(libgtk-x11-2.0.so, 13): image not found.
Could not open library 'libgtk-x11-2.0.so.dylib': dlopen(libgtk-x11-2.0.so.dylib, 13): image not found.
Could not open library 'libgtk-3': dlopen(libgtk-3, 13): image not found.
Could not open library 'libgtk-3.dylib': dlopen(libgtk-3.dylib, 13): image not found.
Could not open library 'libgtk-3.so.0': dlopen(libgtk-3.so.0, 13): image not found.
Could not open library 'libgtk-3.so.0.dylib': dlopen(libgtk-3.so.0.dylib, 13): image not found.
Could not open library 'libgtk-3.so': dlopen(libgtk-3.so, 13): image not found.
Could not open library 'libgtk-3.so.dylib': dlopen(libgtk-3.so.dylib, 13): image not found
Upvotes: 0
Views: 536
Reputation: 5520
Nokogiri tends to complain when your current version of libxml is different from the one it compiled against. That doesn't always cause it to blow up, however. May even be a red herring. I would remove nokogiri from gemfile and see if the error persists. If so, then I'd start removing other stuff. Googling your error message suggests it has to do with a gem that uses libnotify.
Image Not Found Errors after Upgrade to Rails 3.1, how to fix? rake db:migrate error (Function 'inotify_init' not found)
Upvotes: 0