Fixing Jekyll (and Other Ruby Gems [maybe]) After Mojave Update (10.14)
I’m not a huge fan of installing the latest and greatest version of anything until it’s had a chance to bite other people when it breaks. So I was a little annoyed when I finally updated to Mojave (10.14) and received the following error:
This post exists to hopefully provide help to other people when they run into this issue.
My first assumption was to try to just reinstall Jekyll but that didn’t work:
I tried a number of things but what finally did it was making sure I had the latest version of Xcode installed. After I did that I was able to successfully run sudo gem install jekyll
. I also had to reinstall all my other gems but those all went smoothly.
Scott Keck-Warren
Scott is the Director of Technology at WeCare Connect where he strives to provide solutions for his customers needs. He's the father of two and can be found most weekends working on projects around the house with his loving partner.
Top Posts
- Working With Soft Deletes in Laravel (By Example)
- Fixing CMake was unable to find a build program corresponding to "Unix Makefiles"
- Upgrading to Laravel 8.x
- Get The Count of the Number of Users in an AD Group
- Multiple Vagrant VMs in One Vagrantfile
- Fixing the "this is larger than GitHub's recommended maximum file size of 50.00 MB" error
- Changing the Directory Vagrant Stores the VMs In
- Accepting Android SDK Licenses From The OSX Command Line
- Fixing the 'Target class [config] does not exist' Error
- Using Rectangle to Manage MacOS Windows