![]() In the end I started using rbenv to manage ruby installations, and it works flawlessly. I still don't know what I was doing wrong. Usage Install packages (based on package. npm Installation / Update Install npm brew install node Note:Type node -vand npm -vto validate the installation. I got the same error after updating to Big Sur, but this time I couldn't solve it. Gem and Bundler Installation References As a minimal mistake Jekyll theme user, I use the following commands to set up and use npm, gem, and bundler for macOS. Hopefully this will save time people facing the same issue. It looks like a common sense, but it took me a couple of hours to figure it out. ![]() # Use ruby installed by brewĮxport PATH = "/usr/local/opt/ruby/bin:/usr/local/lib/ruby/gems/2.6.0/bin/:$ PATH " So the solution was pretty easy at the end, all I had to do is to find gems/bin folder and add it to my path. Then I tried to see which Jekyll binary is used and realized - for some reason gems were installed using the correct ruby version, but binaries weren't linked properly. ![]() I've tried reinstalling ruby, setting GEM_HOME, altering PATH in /etc/profile and /etc/bashrc, removing and reinstalling gems, but nothing worked. bash_profileĮxport PATH = "/usr/local/opt/ruby/bin:$ PATH "Īfter quick internet search I learned a lot of people are having similar problems after system upgrade, but I couldn't find the solution. Ive updated my ruby development environment and have homebrew and bundler installed. I checked my bash profile and run which ruby to make sure I'm using the one installed by brew, and everything seemed to be in order. Ive been trying to install Jekyll for two days now but dont understand why it doesnt work. bash: /usr/local/bin/jekyll: /System/Library/Frameworks/amework/Versions/2.3/usr/bin/ruby:īad interpreter: No such file or directory ![]() Every time it would fail with the following error: $ jekyll I had one installed via Homebrew, and never had any issues with it.īut after Catalina upgrade, I couldn't run Jekyll. ), and install a separate version for development. As far as I know, on MacOS, it is advisable to leave system Ruby version to the OS (For example users don't have write permission on the system's gems folder. Another Catalina rant, this time about Ruby. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |