I haven’t updated vagrant yet, but I imagine I’ll have to redo this when I do. Running it this way unfortunately results in a bunch of notices being output when run, making it hard to see the important output, but I haven’t found a way around that yet. You could probably remove it if you wanted. I renamed the embedded ruby just in case I needed it. Ln -nfs /opt/local/bin/ruby2.7 /opt/vagrant/embedded/bin/ruby Mv /opt/vagrant/embedded/bin/ruby /opt/vagrant/embedded/bin/xruby prev in thread next in thread List: macports-users Subject: GitX fails to build on El Capitan (New ticket 51559) From: Andrew Long I traced it back to the embedded version of ruby that it comes with, which kept throwing the error SIGSEGV (Address boundary error) even when running directly. But when I tried to just install the compass and sass gems with. When updating to El Capitan, my compass and sass installations had disappeared once again. SASS/Compass with MacPorts on El Capitan. Posted by Armin on Thursday, October 29, 2015. I recently tried to install vagrant on a Mac OS X.11 (El Capitan) machine, but ran into trouble. Installing SASS and compass on Mac 10.11 (El Capitan) with MacPorts.
0 kommentar(er)
