I had dart sass in my macOS Sierra(version 10.12.6). I uninstalled it to install ruby sass, the installation seems to be successful but when I check the version of sass I am getting an error message
$ gem install sass -v3.5.2
Successfully installed sass-3.5.2
Parsing documentation for sass-3.5.2
Done installing documentation for sass after 2 seconds
1 gem installed
Danys-MacBook-Pro:<FOLDERNAME> danyjose$ sass --version
-bash: /Users/danyjose/.nvm/versions/node/v6.0.0/bin/sass: No such file or directory`
I cannot figure out what I am missing here.
Related
I'm running sass --watch to process my css files into scss files. I'm not sure if it's how it works, but I've navigated to the folder in my terminal, and ran the following command:
~/Documents/Website Development/Kedanco/kedanco-website/assets$ sass --watch sass:css
And the following is the error message:
Ignoring bindex-0.5.0 because its extensions are not built. Try: gem
pristine bindex --version 0.5.0
Ignoring binding_of_caller-0.7.2 because its extensions are not built.
Try: gem pristine binding_of_caller --version 0.7.2
Ignoring byebug-9.1.0 because its extensions are not built. Try: gem pristine byebug --version 9.1.0
Ignoring debug_inspector-0.0.3 because its extensions are not built. Try: gem pristine debug_inspector --version 0.0.3
Ignoring ffi-1.9.18 because its extensions are not built. Try: gem pristine ffi --version 1.9.18
Ignoring json-1.8.6 because its extensions are not built. Try: gem pristine json --version 1.8.6
Ignoring nio4r-2.1.0 because its extensions are not built. Try: gem pristine nio4r --version 2.1.0
Ignoring nokogiri-1.8.0 because its extensions are not built. Try: gem pristine nokogiri --version 1.8.0
Ignoring puma-3.10.0 because its extensions are not built. Try: gem pristine puma --version 3.10.0
Ignoring sqlite3-1.3.13 because its extensions are not built. Try: gem pristine sqlite3 --version 1.3.13
Ignoring therubyracer-0.12.3 because its extensions are not built. Try: gem pristine therubyracer --version 0.12.3
Ignoring websocket-driver-0.6.5 because its extensions are not built. Try: gem pristine websocket-driver --version 0.6.5
/home/kelvin/.rvm/gems/ruby-2.4.1/bin/sass:22:in `<main>': undefined method `activate_bin_path' for Gem:Module (NoMethodError)
from /home/kelvin/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `eval'
from /home/kelvin/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `<main>'
I'm familiar with Ruby & Rails, but I'm not using it for this website, it's just a plain static site. Any idea if the target folder was off or I'm using the sass command wrongly?
sass --watch <input folder>:<output folder>
sass-watch watches a directory, and when scss files in the input directory are added/changed/deleted, those changes are reflected in the compiled css files in the output directory.
I'm working with Sass, Compass and Susy on OSX / Terminal. But I can't get Susy to work together with Sass and Compass. What I've done:
sudo gem install sass
sass -v
Returns: Sass 3.3.0 (Maptastic Maple)
sudo gem install compass
This seems to also install sass-3.2.14.gem, then the compass-0.12.3.gem.
compass -v
returns: Compass 0.12.3 (Alnilam)
Everything until this point seems to work fine; I can create a Compass project and work with it. Then I try to install Susy:
sudo gem install susy --pre
or just
sudo gem install susy
This seems to install susy-2.0.0
Than I run:
compass create /Users/tom/Thomas/htdocs/susi4-test -r susy -u susy
And I get this error:
Gem::LoadError on line 2064 of /Library/Ruby/Site/1.8/rubygems/specification.rb: Unable to activate susy-2.0.0, because sass-3.2.14 conflicts with sass (~> 3.3.0)
Run with --trace to see the full backtrace
So there seems to be a problem with the compatibility of the different versions. What can I do to resolve this error?
The dependencies are incompatible: susy 2.0.0 depends on sass ~> 3.3.0 whereas compass 0.12.3 depends on sass = 3.2.14.
The error message says the same:
Unable to activate susy-2.0.0, because sass-3.2.14 conflicts with sass (~> 3.3.0)
You can a) downgrade susy to a version that's working with sass 3.2.14 or b) upgrade compass to a version compatible with sass 3.3.x.
A compatible version is compass 1.0.0 (or later) depending on sass < 3.5, >= 3.3.13. You can install it via
gem update compass
It might be easier to use a gem manager like Bundler. It automatically resolves dependencies and installs the appropriate versions.
gem install compass --pre
when you install compass lastest version will have error like:
ERROR: While executing gem ... (Gem::UnsatisfiableDependencyError)
Unable to resolve dependency: 'compass (= 1.0.0.alpha.19)' requires 'compass-core (~> 1.0.0.alpha.19)'
You should install compass-core first
gem install compass-core
The best way without a doubt is to install Susy via the Compass Susy Plugin. This will avoid conflicts with other Compass projects that require the current version.
Commands:
gem install compass
gem install compass-susy-plugin
I am trying to use SASS for the first time, i have installed the latest version but get errors in the terminal
stuarts-imac:css stuartcookney$ sass --watch main-style.scss
Sass is watching for changes. Press Ctrl-C to stop.
write main-style.css
LoadError: cannot load such file -- listen/version
Use --trace for backtrace.
It compiles the css file but something is broken as any other changes that i make they do not update.. what is wrong?
Just tried a mix of some answers, on Ubuntu 21:
First:
sudo apt-get install ruby-listen
And then:
sudo gem install sass-listen
It's now posible to sass src:dst --watch
Thank you #dimetrodon, #maxime-lorant and #kevin-mack
Lubuntu fixed with a simple:
sudo gem install sass-listen
On Linux Mint 18.1.
You can help it
sudo apt-get install ruby-listen
This is what fixed it for me and some others:
sudo gem uninstall listen --version 2.7.0
sudo gem install listen --version 2.4.1
I was receiving the same error. The output with the --trace option will contain something like the following near the top:
`require': cannot load such file -- rb-inotify
I have no experience with ruby but seems like sass is simply trying to load in a dependency which isn't there. You can use gem to resolve it:
gem install rb-inotify
I've tried all above:
gem install listen --version 2.4.1
gem install sass-listen
apt-get install ruby-listen
gem install rb-inotify
completely uninstalled sass and ruby and reinstalled.
The only thing that worked was to ditch ruby-sass completely and install dart-sass instead.
In Ubuntu (checked in Ubuntu 20)
sudo apt install sass sass-listen
I should probably start by saying that I am new to rails. This specific error message came up as i was trying to run bundle install. Error pops up once installation gets to json.
=============================================================================
Installing json (1.8.0)
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
D:/Dev/RailsInstaller/Ruby1.9.3/bin/ruby.exe extconf.rb
D:/Dev/RailsInstaller/Ruby1.9.3/bin/ruby.exe: No such file or directory -- extconf.rb (Loa
dError)
Gem files will remain installed in D:/Dev/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gem
s/json-1.8.0 for inspection.
Results logged to D:/Dev/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/json-1.8.0/ext/
json/ext/generator/gem_make.out
An error occurred while installing json (1.8.0), and Bundler cannot continue.
Make sure that gem install json -v '1.8.0' succeeds before bundling.
===============================================================================
gem_make.out log file is showing
===============================================================================
D:/Dev/RailsInstaller/Ruby1.9.3/bin/ruby.exe extconf.rb
D:/Dev/RailsInstaller/Ruby1.9.3/bin/ruby.exe: No such file or directory -- extconf.rb (LoadError)
===============================================================================
I already tried running gem install json and essentially got the same error message. DevKit is already installed. Reinstalling it made no difference.
Ruby version is 1.9.3p392
Rails version is 3.2.13
OS is Windows7 64bit
installation was completed using rubyinstaller.
Any help will be greatly appreciated.
I got the same error when trying to install Cucumber using the Gemfile provided in The Cucumber Book (p. 299) and also with gem install json.
When trying gem install cucumber it worked:
Fetching: multi_json-1.8.0.gem (100%)
Successfully installed multi_json-1.8.0
...
hth
Frank
I want to use qt5's QtWebKit with capybara-webkit.
brew uninstall qt
Uninstalling /usr/local/Cellar/qt/4.8.4...
brew install qt5
This formula is keg-only: so it was not symlinked into /usr/local.
🍺 /usr/local/Cellar/qt5/5.0.2: 3103 files, 140M, built in 60.9 minutes
If I force brew to create the symlinks for qt5 I can build the native extension for capybara-webkit ..
brew link --force qt5
Linking /usr/local/Cellar/qt5/5.0.2... 122 symlinks created
gem install capybara-webkit -v '1.0.0'
Successfully installed capybara-webkit-1.0.0
.. but webkit_server crashes hard ..
bundle exec rake test:integration
Errno::EADDRNOTAVAIL: Can't assign requested address - connect(2)
dyld: Library not loaded: /private/tmp/qt5-KytU/qt-everywhere-opensource-src-5.0.2/qtwebkit/lib/QtWebKit.framework/Versions/5/QtWebKit
Referenced from: /usr/local/opt/qt5/lib/QtWebKitWidgets.framework/Versions/5/QtWebKitWidgets
Reason: image not found
See full osx crash report.
I tried installing capybara-webkit with LDFLAGS and CPPFLAGS but webkit_server still crashes hard.
env LDFLAGS=-L/usr/local/opt/qt5/lib \
CPPFLAGS=-I/usr/local/opt/qt5/include \
gem install capybara-webkit -v '1.0.0'
NOTE: IAmNaN here... this answer worked find for El Cap and Yosemite but it is no longer relevant as of MacOS Sierra. Instead follow the instructions from Thoughtbot. To summarize...
Download and install a new Qt from here.
Edit ~/Qt5.5.1/5.5/clang_64/mkspecs/features/mac/default_pre.prf.
Around line 15 find and replace -find xcrun 2 with -find xcodebuild 2.
Save and run PATH=~/Qt5.5.1/5.5/clang_64/bin:$PATH gem install capybara-webkit
Now back to our regularly scheduled answer....
I got this to work on OSX Yosemite. The reason for building against Qt5 was to get some fixes not in Qt4 that prevented capybara-webkit from using font and stylesheet assets in some circumstances.
Comment out the capybara and capybara-webkit gems from your gemfile. Then:
bundle
gem uninstall capybara-webkit
gem uninstall capybara # if it complains about dependencies 'gem uninstall' them first
brew remove qt
brew remove qt5 # if you've been playing around
From a clean environment (restart your terminal):
brew tap homebrew/versions
brew install qt55
brew linkapps qt55
brew link --force qt55
Uncomment capybara and capybara-webkit in the gemfile and then:
bundle install
Note: You may safely ignore the "brew unlink" warnings issued by brew doctor.
Two years later, the same steps from my question now work. Thanks, whoever fixed it.
gem uninstall --all capybara-webkit
brew remove qt
brew install qt5
brew linkapps qt5 # optional?
brew link --force qt5
gem install capybara-webkit
After installing qt5, I no longer see this message from my test suite:
WARNING: The next major version of capybara-webkit will require at least version 5.0 of Qt.
Uninstalling the capybara gem is not necessary (as other answers suggest) because it has no native extensions, thus no direct dependency on QT.
According to https://github.com/thoughtbot/capybara-webkit/issues/885 , QT stopped working with webkit at version 5.6. However, there is a qt55 brew available, so use qt55 (instead of qt5) in the answers above.
I suggest to brew update, brew remove qt5 and brew install qt5, because I find on my system, that:
xcrun otool -L /usr/local/Cellar/qt5/5.0.2/lib/QtWebKitWidgets.framework/Versions/5/QtWebKitWidgets
[snip]
/usr/local/Cellar/qt5/5.0.2/src/qtwebkit/lib/QtWebKit.framework/Versions/5/QtWebKit (compatibility version 5.0.0, current version 5.0.2)
So Qt5 does link against QtWebKit and the link is valid on my system in contrast to yours.
Therefore the suggestion to reinstall. If homebrew installs the prebuilt bottle and still has this issue, please report on Homebrew's issue tracker on github. I installed mine from source.
However, I guess an upstream issue (a minor one) is that the link points into src which should probably lib. But that is up to Qt to fix.