Skip to main content

Install current SBCL on OS X

You must have Command Line Tools installed. If you don't, this tutorial is not for you. Google: installation of XCode and Command Line Tools.

Normally, I use brew to install things (when it offers a solution), but in this case the keg version was a couple minor version's off. And, there had been sufficient addition's that motivated me to want the current release. So, building from source was the path of least resistance.

First, what not to do:

The note's caution against using OS X's Terminal, as their make.sh script pukes a shit-ton of text during the build, and according to them, it can slow the build. I did not experience an issue with this, compared to other builds I've done in the past.  BUT, they also say build can be accomplished with other LISP's installed (you must have a lisp installed prior to building). OMFG, unless you want to wait a month of Sunday's, my experience building with CLISP was slower than the Molasses in January.  Do yourself a favor if you don't have an install of sbcl already  (likely from brew as it is a few minor version's behind the current one at this time), install sbcl from brew FIRST!!!  Build went so much faster.

So, here's what I recommend:

Install sbcl using brew.  If you don't already have brew installed, why the frak not?  Install it. You can thank me later.

Ok, so you've installed sbcl using brew. Now, download the current version from sbcl's website,  untar/unbzip it, and cd into the new directory. For illustrative purposes, in my case it's /sbcl-1.2.5. Once inside, you can follow their prescribed method (you may need to sudo first):

sh make.sh

It will pick-up the current install of sbcl and use it. Once it's done, uninstall brew's version of sbcl:

brew uninstall sbcl

Now, (again, you may need to sudo first):

sh install.sh

You should now have the current sbcl available in your path at:

/usr/local/bin/sbcl
Labels:
Location: Portland, OR, USA

Comments

Post a Comment

Popular posts from this blog

React Simplicity

This is just a quick intro to React to show how easy it is on a very basic level. React is often compared to Angular, but the two are very different: Angular is more of a framework , whereas React is more of a library . So, with React, we can make Components, and in so doing, we can intersperse plain Javascript to instill behavior. This article is not showing (or using) best practices, or a recommended structure. It's purpose is only to show how easy the basic mechanics of React are. Let's grab the getting started cli from React's page npm install -g create-react-app create-react-app my-app cd my-app npm start After this is done, and you have the project displayed in your browser, let's experiment. A boiler-plate header we can use for each new class can be as simple as: /src/Foo.js import React, { Component } from 'react'; class Foo extends Component { render(){ return(); } } export default Foo; So, all that we need to change to get st
Post a Comment
Read more

Screen Scraping in Ruby with Watir and Nokogiri

I was given an interesting challenge to scrape some data from a specific site.  Not to write a completed, packaged solution, but rather just to scrape the data.  The rub being, the site uses Javascript paging, so one couldn't simply use something like Mechanize.  While a self-contained product would require inclusion of V8 (as the Javascript would need to be run and evaluated), to just scrape the data allows making use of whatever is easy and available.  Enter Watir . Watir allows "mechanized/automated" browser control.  Essentially, we can script a browser to go to pages, click links, fill out forms, and what have you.  It's mainstay is in testing, but it's also pretty damned handy in cases where we need some Javascript on a page processed... like in this case.  Keep in mind though, it is literally automating a browser, so you'll see your browser open and navigate to pages, etc. when the script runs.  But, there is also a headless browser option.  This is
Post a Comment
Read more